Is Selena 7.0.4 EAP just getting worse?

Is it just me or is the eap builds for Selena 7.0.4 just getting more and more "buggy" for every new eap?
I am still running build 7782 but have tried every eap since but always ended up with going back to 7782. And now with build 7860, I managed to crash IDEA just by pressing CTRL-F4 to close an xml file (it's been many years since I last managed to crash IDEA....)


BTJ

6 comments
Comment actions Permalink

Define "crash IDEA". If it just completely died without trace then it's likely
a VM crash, and probably not IDEA's fault. Have a look at the logs.

Is it just me or is the eap builds for Selena 7.0.4 just getting more
and more "buggy" for every new eap?

I am still running build 7782 but have tried every eap since but
always ended up with going back to 7782. And now with build 7860, I
managed to crash IDEA just by pressing CTRL-F4 to close an xml file
(it's been many years since I last managed to crash IDEA....)

BTJ



0
Comment actions Permalink

Hmmmm... Ok, there is a hs log file that says...:

#

  1. An unexpected error has been detected by Java Runtime Environment:

#

  1. SIGSEGV (0xb) at pc=0x064ac2ae, pid=13520, tid=2059746192

#

  1. Java VM: Java HotSpot(TM) Server VM (10.0-b22 mixed mode linux-x86)

  2. Problematic frame:

  3. V

#

  1. If you would like to submit a bug report, please visit:

  2. http://java.sun.com/webapps/bugreport/crash.jsp

  3. The crash happened outside the Java Virtual Machine in native code.

  4. See problematic frame for where to report the bug.

#

-


T H R E A D -



Current thread (0x08141400): JavaThread "CompilerThread1" daemon
.....................




Strange thing is that it happend almost at once after starting the new build.....


BTJ

0
Comment actions Permalink

this most likely looks like a vm bug

0
Comment actions Permalink

It does seem like I've run into more bugs in this EAP than with most of the
previous post 7.0 EAP builds.

In particular these were all new bugs introduced during 7.0.4 that I have
personally experienced
http://www.jetbrains.net/jira/browse/IDEADEV-26551
http://www.jetbrains.net/jira/browse/IDEA-18034
http://www.jetbrains.net/jira/browse/IDEADEV-27071
http://www.jetbrains.net/jira/browse/IDEADEV-26483
http://www.jetbrains.net/jira/browse/IDEADEV-26164 (although I think this
was introduced in 7.0.3)




"Bjørn T Johansen" <no_reply@jetbrains.com> wrote in message
news:23992082.59841212562711938.JavaMail.jive@app4.labs.intellij.net...

Is it just me or is the eap builds for Selena 7.0.4 just getting more and
more "buggy" for every new eap?
I am still running build 7782 but have tried every eap since but always
ended up with going back to 7782. And now with build 7860, I managed to
crash IDEA just by pressing CTRL-F4 to close an xml file (it's been many
years since I last managed to crash IDEA....)

>
>

BTJ


0
Comment actions Permalink

I haven't experienced a single IDEA crash since 7.0 was released. The previous 7.0.4 EAP had a few performance problems, but the recently released build is working flawless for me.

0
Comment actions Permalink

Unless IDEA contains native code libraries that could trash the JVM's memory, that is by definition a JVM bug.

RRS

0

Please sign in to leave a comment.