You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by Andrew Feller <af...@lsu.edu> on 2009/04/27 16:51:47 UTC
Segmentation fault when running Jmeter 2.3.2 r665936
PROBLEM: Jmeter crashes with segmentation fault when during long runs
ENVIRONMENT: Mac OS X Leopard, Apple Java 6, Jmeter 2.3.2 r665936
JMETER SETTINGS: Xms=512m, Xmx=512m
JMETER COMMAND LINE MESSAGES:
Invalid memory access of location fffffff8 rip=010f374c
/Applications/jakarta-jmeter-2.3.2/bin/jmeter: line 90:
518 Segmentation fault
java $JVM_ARGS $ARGS -jar `dirname $0`/ApacheJMeter.jar "$@"
[1]+ Exit 139 /Applications/jakarta-jmeter-2.3.2/bin/jmeter
For the past week or two, Jmeter is consistently crashing on me, and I
cannot figure out why. When it started, I enabled logging of garbage
collection information, which shows cycles of several partial GCs with a
full GC occurring periodically. Has anyone come across this issue? What
can I do?
Thanks,
Andrew
--
Andrew Feller, Analyst
LSU University Information Services
200 Frey Computing Services Center
Baton Rouge, LA 70803
Office: 225.578.3737
Fax: 225.578.6400
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: Segmentation fault when running Jmeter 2.3.2 r665936
Posted by sebb <se...@gmail.com>.
On 27/04/2009, Andrew Feller <af...@lsu.edu> wrote:
> PROBLEM: Jmeter crashes with segmentation fault when during long runs
> ENVIRONMENT: Mac OS X Leopard, Apple Java 6, Jmeter 2.3.2 r665936
> JMETER SETTINGS: Xms=512m, Xmx=512m
> JMETER COMMAND LINE MESSAGES:
>
> Invalid memory access of location fffffff8 rip=010f374c
> /Applications/jakarta-jmeter-2.3.2/bin/jmeter: line 90:
> 518 Segmentation fault
> java $JVM_ARGS $ARGS -jar `dirname $0`/ApacheJMeter.jar "$@"
> [1]+ Exit 139 /Applications/jakarta-jmeter-2.3.2/bin/jmeter
>
> For the past week or two, Jmeter is consistently crashing on me, and I
> cannot figure out why. When it started, I enabled logging of garbage
> collection information, which shows cycles of several partial GCs with a
> full GC occurring periodically.
This sounds normal.
> Has anyone come across this issue? What
> can I do?
JMeter is a pure Java application, and so any JVM crashes must be due
to bugs in the JVM. Pure Java code can cause a JVM to exit, e.g. if it
uses up all the memory, but a segmentation fault is definitely a bug
in the JVM.
[Of course, JNI code can easily cause a crash, but JMeter does not use
any JNI code.]
I suggest you ensure you have got the latest JVM updates (and any OS
updates that it may require). If the JVM still crashes, you will need
to report this to the JVM provider.
> Thanks,
> Andrew
> --
> Andrew Feller, Analyst
> LSU University Information Services
> 200 Frey Computing Services Center
> Baton Rouge, LA 70803
> Office: 225.578.3737
> Fax: 225.578.6400
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org