Bugzilla – Full Text Bug Listing
| Summary: | Eclipse sometimes crashes when switching workspaces or restarting after installing updates | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Mirko Seifert <mirko.seifert> | ||||||||
| Component: | IDE | Assignee: | Platform-UI-Inbox <Platform-UI-Inbox> | ||||||||
| Status: | RESOLVED NOT_ECLIPSE | QA Contact: | |||||||||
| Severity: | major | ||||||||||
| Priority: | P3 | CC: | hsoliwal, mirko.seifert, pwebster, remy.suen, sw | ||||||||
| Version: | 3.6 | ||||||||||
| Target Milestone: | --- | ||||||||||
| Hardware: | PC | ||||||||||
| OS: | Windows 7 | ||||||||||
| Whiteboard: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Mirko Seifert
Please attach the log. That would help determining the problem Where can I find the log file? Created attachment 170746 [details]
A screenshot of the windows crash dialog
(In reply to comment #2) > Where can I find the log file? It should be in <your workspace dir>\.metadata\.log I had a look at the .log files and since I could not find anything that indicated a crash, I deleted the .log files (in both workspaces) to restart Eclipse and to reproduce the problem using a clean log file. Unfortunately, now Eclipse does not start up anymore. The splash screen is shown for a short time and the Eclipse closes without further error messages. Rather, an error is reported by the JVM, which I will attach. Created attachment 170748 [details]
JVM crash log file
I was able to reproduce the same bug with 3.6M7, which is able to start using my workspaces. I will attach the log files from both workspaces (the crash occurred while switching from one to another). However, the last entry in both log files is from yesterday (2010-06-01), whereas the crash occured today (2010-06-02) - just a few minutes ago. Created attachment 170751 [details]
Workspace Log files
Short update: I installed the most recent Java 5 SDK from the Oracle Website (1.5.0_22-b03), but the problem is still there. Can you try only with the SDK (without any third party plugins) on a fresh workspace? I guess it might have to do with Subclipse. I've tried again with a clean installation (directly after unzipping eclipse-SDK-3.6RC2-win32-x86_64.zip). I've created two empty directories for the workspaces. When switching from the first to the second I faced the same error (crash with Windows problem reporting dialog). No log files were created in any of the two workspaces. Hitesh, If you are on Win7 can you try this? (In reply to comment #11 & comment 12) > I've tried again with a clean installation (directly after unzipping > eclipse-SDK-3.6RC2-win32-x86_64.zip). I've created two empty directories for > the workspaces. When switching from the first to the second I faced the same > error (crash with Windows problem reporting dialog). > > No log files were created in any of the two workspaces. > Hitesh, > > If you are on Win7 can you try this? I've been running the 32-bit version of Win7 for a while now, I haven't come across such a crash so far and neither can I reproduce it now (using eclipse-SDK-3.6RC3) If you try Java 6 does it work? I use Windows 7 and haven't seen this problem before and I haven't been hearing complaints on IRC. I've now installed the latest Java 6 SDK from oracle.com (build 1.6.0_20-b02 64bit). Indeed I can't reproduce both crashes reported here (the one at startup and the other one when switching workspaces) anymore. This is fine for me, but since the official Eclipse Download Site recommends to use a Java 5 SDK, this is probably not a general solution. Is it? (In reply to comment #15) > This is fine for me, but since > the official Eclipse Download Site recommends to use a Java 5 SDK, this is > probably not a general solution. Is it? Since it works with a Java 6 download but not a Java 5 download, it sounds like this may be a VM bug and not an issue with your Eclipse installation. I totally agree that this is a bug in the VM. The official website about VM compatibility (http://www.eclipse.org/downloads/moreinfo/jre.php) states that Eclipse is tested with Sun Java 2 Standard Edition 5.0 Update 11. It does not make any statements about the 64bit version of Windows and/or Eclipse. If Eclipse (or Helios) is tested on the 64bit Platforms using the Java 6 SDK, it should say so. I don't mind installing Java 6, but its probably not a good idea to tell people that Java 5 is fine if that is not the case for Helios. (In reply to comment #17) > The official website about VM compatibility > (http://www.eclipse.org/downloads/moreinfo/jre.php) states that Eclipse is > tested with Sun Java 2 Standard Edition 5.0 Update 11. It does not make any > statements about the 64bit version of Windows and/or Eclipse. If Eclipse (or > Helios) is tested on the 64bit Platforms using the Java 6 SDK, it should say > so. That page looks quite old. If we're talking 3.6 you want to look at the 3.6 plan. http://eclipse.org/projects/project-plan.php?projectid=eclipse.platform#target_environments > I don't mind installing Java 6, but its probably not a good idea to tell people > that Java 5 is fine if that is not the case for Helios. As I mentioned in comment 14, we have not been seeing a flood of bugs over Java 5 not working. At the moment, there is insufficient evidence to simply state that Java 5 does not work for Eclipse 3.6. Ok, so for 3.6 the official target platform for Win7-64bit is "Sun Java 5 Update 22". Let me know if I can provide further information to track down the problem. (In reply to comment #19) > Ok, so for 3.6 the official target platform for Win7-64bit is "Sun Java 5 > Update 22". > > Let me know if I can provide further information to track down the problem. The problem indicated by your stack trace seems to be a VM problem (and you mentioned a specific version of the Oracle VM). It died in java.util.Properties and ntdll.dll You would need to open a bug with them. In the mean time, the only solution is to change VMs (which it sounds like you have done). PW |