phpstorm
Java HotSpot(TM) 64-Bit Server VM (build 17.1-b03, mixed mode)[YourKit Java Profiler 8.0.26] JVMTI version 3001016d; 17.1-b03; Sun Microsystems Inc.; mixed mode, sharing; Linux; 64-bit JVM[YourKit Java Profiler 8.0.26] Profiler agent is listening on port 10001...[YourKit Java Profiler 8.0.26] *** HINT ***: To get profiling results, connect to the application from the profiler UI[YourKit Java Profiler 8.0.26] JVMTI version 3001016d; 17.1-b03; Sun Microsystems Inc.; mixed mode, sharing; Linux; 64-bit JVM[YourKit Java Profiler 8.0.26] Profiler agent is listening on port 10001...[YourKit Java Profiler 8.0.26] *** HINT ***: To get profiling results, connect to the application from the profiler UI## A fatal error has been detected by the Java Runtime Environment:## SIGSEGV (0xb) at pc=0x000000000002c436, pid=14472, tid=140083640334096## JRE version: 6.0_22-b04# Java VM: Java HotSpot(TM) 64-Bit Server VM (17.1-b03 mixed mode linux-amd64 compressed oops)# Problematic frame:# C 0x000000000002c436## An error report file with more information is saved as:# /root/sources/PhpStorm-98.521/bin/hs_err_pid14472.log## If you would like to submit a bug report, please visit:# http://java.sun.com/webapps/bugreport/crash.jsp#/root/sources/PhpStorm-98.521/bin/webide.sh: line 115: 14472 Aborted $WEBIDE_JDK/bin/java $JVM_ARGS -Djb.restart.code=88 $WEBIDE_MAIN_CLASS_NAME $*laptop:~# phpstormJava HotSpot(TM) 64-Bit Server VM (build 17.1-b03, mixed mode)[YourKit Java Profiler 8.0.29] JVMTI version 3001016d; 17.1-b03; Sun Microsystems Inc.; mixed mode, sharing; Linux; 64-bit JVM[YourKit Java Profiler 8.0.29] Profiler agent is listening on port 10001...[YourKit Java Profiler 8.0.29] *** HINT ***: To get profiling results, connect to the application from the profiler UI
well, it surely looks impressive, but what you were doing when you got it?
I started PS and got a message that a new version is available (some updates)
I choose upgrade and restart.
After the download and upgrade process was done...
It restarted automatically and crashed.
Since then, i started PS and it seems to work just fine.
I was just letting you know.
Maybe it can be useful to you?
If you think you need some more info, please let me know
Nadav :-)
Well, the hs_err_pid14472.log with details it says it saved might be useful (the crash message by itself is not)
I am attaching the file to this post
Attachment(s):
hs_err_pid14472.log.zip
Well, EAP builds contain built-in profiler that uses native code - and it may crash in some rare occasions. Nothing critical, thanks for reporting.
cool :-)
I am not using the profiler and I was wondering if I can disable it?
(regardless, to this issue)