Bugzilla – Full Text Bug Listing
| Summary: | When opening a particular workplace that had open editors and the system shut down, eclipse hangs on re-open. | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Steve Owens <steve> |
| Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | daniel_megert |
| Version: | 3.6.2 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
Steve please try 3.7 RC4: http://download.eclipse.org/eclipse/downloads/drops/S-3.7RC4-201106030909/index.php *** This bug has been marked as a duplicate of bug 327471 *** |
Build Identifier: M20100211-1343 When I try to open up a workspace I was working in, eclipse hangs in the splash screen while Loading workbench. The .log file in the work space has the following entries: !SESSION 2011-06-05 11:02:43.409 ----------------------------------------------- eclipse.buildId=M20100211-1343 java.version=1.6.0_24 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Command-line arguments: -data /home/stephen/Maven/hulu -os linux -ws gtk -arch x86_64 !ENTRY org.eclipse.core.resources 2 10035 2011-06-05 11:02:45.820 !MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes. !ENTRY org.eclipse.jdt.core 4 4 2011-06-05 11:02:47.149 !MESSAGE Unable to read variable and containers file !STACK 0 java.io.EOFException at java.io.DataInputStream.readInt(DataInputStream.java:375) at org.eclipse.jdt.internal.core.JavaModelManager$VariablesAndContainersLoadHelper.loadInt(JavaModelManager.java:3275) at org.eclipse.jdt.internal.core.JavaModelManager$VariablesAndContainersLoadHelper.loadVariables(JavaModelManager.java:3341) at org.eclipse.jdt.internal.core.JavaModelManager$VariablesAndContainersLoadHelper.load(JavaModelManager.java:3144) at org.eclipse.jdt.internal.core.JavaModelManager.loadVariablesAndContainers(JavaModelManager.java:2980) at org.eclipse.jdt.internal.core.JavaModelManager.startup(JavaModelManager.java:4623) Rest of the stack trace is ommited. The problem is it doesn't tell you what to do to bring workspace back to a state of usability. Reproducible: Always Steps to Reproduce: 1. Open this workspace. 2. It hangs.