Community
Participate
Working Groups
Build Identifier: 20110916-0149 I'm running Eclipse Indigo 3.7.1 on Ubuntu 11.10 (Oneiric Ocelot) 64-bit with the Oracle/Sun JRE 1.6.0_30-b12. I'm doing Java development. I've started seeing random crashes today with an Eclipse on Ubuntu installation I've been using for 3 months. The only changes I'm aware of are the standard Ubuntu updates, which I install as they are available. I know my Linux kernel was updated early last week. But Eclipse ran fine all through last week. These crashes started today. I say they are random because I haven't been able to determine any consistency in what I've been doing when they occurred. The first one occurred while I was typing text into a string (inside auto-entered double quotes, a method parameter). I entered a right paren inside the string and it apparently thought I wanted to skip out of the method; it placed the cursor after the right paren that closed the method call. I move the cursor back to where I wanted in the string and when I entered the right paren again, it crashed. I started it up again, after pausing to think that was really weird behavior. I'd lost all the changes I made since I last saved (about an hour of changes). I selected a block of commented-out code and hit DEL to delete it and it immediately crashed. That's when I started searching the Internet for clues to its behavior. After a few minutes, I started Eclipse again and I worked for over an hour, saving my changes frequently. Then it crashed when I double-clicked on the name of a method; I wanted to search for all references to the method. It crashed immediately after the method name was highlighted, before I could right-click to bring up the context menu. While searching the Internet for clues, I thought this behavior was related to bug 345979 (https://bugs.eclipse.org/bugs/show_bug.cgi?id=345979). But it seems to be different. And that bug was resolved in 3.7.1. I will attach the three error logs it created for the crashes. The PIDs in the names are in the order of the crashes I described above. I will also attache the info from the Configuration tab in the About/Installation Details dialog. Reproducible: Sometimes
Created attachment 210286 [details] Error log Error log from first crash described.
Created attachment 210287 [details] Error log Error log from second crashed described.
Created attachment 210288 [details] Error log Error log from third crashed described.
Created attachment 210289 [details] Eclipse configuration details Eclipse configuration details from About/Installation Details/Configuration.
(In reply to comment #0) > [...] The only changes I'm aware of are the standard > Ubuntu updates, which I install as they are available. I know my Linux kernel > was updated early last week. But Eclipse ran fine all through last week. These > crashes started today. Any chance that java got updated? On my Ubuntu 11.04 java was updated about a week ago. Thanks for the detailed description but I don't think we can map your actions to the different crashes. > While searching the Internet for clues, I thought this behavior was related to > bug 345979 (https://bugs.eclipse.org/bugs/show_bug.cgi?id=345979). But it seems > to be different. And that bug was resolved in 3.7.1. I don't see much similarity, actually. > I will attach the three error logs it created for the crashes. The PIDs in the > names are in the order of the crashes I described above. I will also attache > the info from the Configuration tab in the About/Installation Details dialog. The logs all show different patterns of crashing. The first one looks weirdest to me: it says that Java code from ASTConverter directly called into native code at address 0x0000000000000005, yet nowhere in the JDT do we directly call native code. The second and third logs show crashes at different locations inside libjvm.so. My guess would be that either your java installation is badly broken or due to the randomness I could even think of a hardware problem. With such different logfiles it's hard to come up with a reasonable hypothesis that would explain them all.
I will research my installation of Java and see if it was updated. I have a couple older installations of the JRE still around. Should be easy to try a slightly older version to see what happens. I will report back what I find.
This all turned out to be a hardware problem ... bad memory! My whole computer started degrading and diagnostics discovered bad memory. Taking that out fixed everything. I very much apologize for bothering anyone with this. I did learn much about how to install the Oracle/Sun JDK on Ubuntu now that it is longer in the repositories.
Thanks for reporting back. Yeah, sometimes suspecting hardware problems is a lame excuse, but when they occur they can just produce about any conceivable behavior.
