Bugzilla – Full Text Bug Listing
| Summary: | exception during refresh prevents startup after crash | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Jason Rogers <jason> | ||||||
| Component: | Resources | Assignee: | Platform-Resources-Inbox <platform-resources-inbox> | ||||||
| Status: | RESOLVED DUPLICATE | QA Contact: | |||||||
| Severity: | major | ||||||||
| Priority: | P3 | CC: | eduard, mkwong | ||||||
| Version: | 3.0 | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | PC | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
|
Description
Jason Rogers
Created attachment 13833 [details]
Log with error stack in it
Sorry, I miscopied the second error in the original post. I am attaching the
log that has only the errors from trying to restart.
Well, I backed up my current workspace, untarred a backup from 1:00AM today and everything is working. I had to copy over my changed files from the "corrupt" workspace (which was a hassle) but at least I am back in business. I am therefore changing the severity of the bug from "blocker" to "major". Move to Platform/Runtime This has just happened again. Same error, different cause. This time Eclipse locked up on me and I shut it down forcefully. Something strange seems to have happened to your workspace. Moving to resources for comment. Yes, something strange did happen to the workspace. My point in posting the bug was to find out what. It seems to me that after such shutdowns (OutOfMemoryCrash in one instance, ForcedShutdownAfterHang in another instance) you should /still/ be able to restart Eclipse. The errors in the log may be misleading, but if they aren't it sounds like a classpath issue. I don't know why an unexpected shutdown would cause classpath problems. OK, now this is getting ridiculous. I wonder if it has something to do with the plugins I have installed. I am experiencing the same behavior today. This time, Eclipse popped up the OutOfMemory dialog and gave me the choice to close the workbench or not. I decided not to close, got out of the dialog box, then closed Eclipse manually. When I restart I get the same error. You are correct, no matter how you crashed you should be able to start Eclispe again. How big is your workspace? Are you able to zip it and send it to us? Note that in your command-line arg you are probably getting the OutofMemory because of the -Xmx25M. Did you mean to type "256M" instead? The commandline is actually: /opt/eclipse/gtk/3.0Final/eclipse -data /home/jrogers/workspace -vmargs -Xmx96M -Xverify:none -XX:+UseParallelGC -XX:PermSize=20M -XX:MaxNewSize=32M -XX:NewSize=32M -Xms64m I up'ed the -Xmx after the first crash. As far as the size of the workspace, it is pretty large. I TARed and GZIPed the .metadata directory and it is 7.3MB. I can attach it if you would like. Can you delete \.metadata\.plugins\org.eclipse.core.resources\.history before attaching? (just contains local history) Unfortuanatly with crashes the interesting thing is "how did we get in this state?" and its hard to figure that out since it already happened. But I can try to set up a new workspace with your .metadata and go from there... I removed .metadata/.plugins/org.eclipse.core.resources/.history and rearchived it, but that only takes it from 7.3MB to 7.2MB. I ran "du -hc" on .metadata and it seems that the most space is contributed by .metadata/.plugins/org.eclipse. jdt.core, weighing in at 19MB. There are a bunch of *.index files there (eg. 71478105.index). Can I take those out, or do you need them? Also, I have TARed and BZIPed the directory and gotten it down to 5.3M, so if that is acceptable I will attach it. Sure, get rid of the index files. FYI: I'm away for a week or so (starting tomorrow) so I will not be able to look at this for a bit. (unless someone else gets a chance while I'm gone) Created attachment 14083 [details]
.metadata directory TARed and BZIPed
The .metadata directory has everything from the latest crashed workspace except
for:
- .metadata/.plugins/org.eclipse.core.resources/.history
- .metadata/.plugins/org.eclipse.jdt.core/*.index
Thanks for looking into this. Enjoy your vacation. *** Bug 57344 has been marked as a duplicate of this bug. *** I'm also seeing 'OutOfMemory' errors. I have a little more detail however. I was debugging a plugin, so I was able to trap the OutOfMemory exception within the debugger, and the stack trace in my case is as follows: Thread [main] (Suspended (exception OutOfMemoryError)) ResourceTransfer.nativeToJava(TransferData) line: 160 Clipboard.getContents(Transfer, int) line: 304 Clipboard.getContents(Transfer) line: 236 PasteAction$1.run() line: 186 UISynchronizer(Synchronizer).syncExec(Runnable) line: 147 UISynchronizer.syncExec(Runnable) line: 28 Display.syncExec(Runnable) line: 3255 PasteAction.updateSelection(IStructuredSelection) line: 181 PasteAction(BaseSelectionListenerAction).selectionChanged(IStructuredSelection) line: 124 RefactorActionGroup.updateActionBars() line: 154 MainActionGroup.updateActionBars() line: 315 ResourceNavigator.updateActionBars(IStructuredSelection) line: 1206 ResourceNavigator.createPartControl(Composite) line: 275 ViewReference.createPartHelper() line: 310 ViewReference.createPart() line: 185 ViewReference(WorkbenchPartReference).getPart(boolean) line: 559 WorkbenchPage$ActivationList.setActive(IWorkbenchPartReference) line: 3399 WorkbenchPage.onActivate() line: 2089 WorkbenchWindow$5.run() line: 2359 BusyIndicator.showWhile(Display, Runnable) line: 69 WorkbenchWindow.setActivePage(IWorkbenchPage) line: 2341 WorkbenchWindow.busyOpenPage(String, IAdaptable) line: 695 Workbench.busyOpenWorkbenchWindow(String, IAdaptable) line: 617 Workbench.openFirstTimeWindow() line: 1168 WorkbenchConfigurer.openFirstTimeWindow() line: 180 IDEWorkbenchAdvisor(WorkbenchAdvisor).openWindows() line: 706 Workbench.init(Display) line: 981 Workbench.runUI() line: 1541 Workbench.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 315 PlatformUI.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 143 IDEApplication.run(Object) line: 103 PlatformActivator$1.run(Object) line: 230 EclipseStarter.run(Object) line: 371 EclipseStarter.run(String[], Runnable) line: 160 NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method] NativeMethodAccessorImpl.invoke(Object, Object[]) line: 39 DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 25 Method.invoke(Object, Object[]) line: 324 Main.invokeFramework(String[], URL[]) line: 330 Main.basicRun(String[]) line: 274 Main.run(String[]) line: 977 Main.main(String[]) line: 952 The variables are as follows: this= ResourceTransfer (id=46) transferData= TransferData (id=55) bytes= byte[25] (id=58) in= DataInputStream (id=60) count= 1869768494 That count looks suspicious. Eduard, your OOM is unrelated to this PR, which is caused by a corrupted file. OOMs are not always bugs, it can be just insufficient memory being provided to the Java VM for the operation being performed. You can use the VM arg -Xmx<size>m to change the maximum of memory allowed to a Java application (size in megabytes), for instance: eclipse [any Eclipse args you might have] -vmargs -Xmx512m Eduard, I suggest entering a separate bug report against Platform UI in your case. I agree the "count" variable looks suspicious. It looks like the data on the system clipboard is somehow being corrupted. In any case, it's unrelated to this bug. Updating title to make it clear that not all OutOfMemoryErrors are related. Here is the relevant snippet from the log file that caused the startup failure: java.lang.IllegalArgumentException: Path must include project and resource name: /Salesforce.com Web Application at org.eclipse.core.internal.utils.Assert.isLegal(Assert.java:58) at org.eclipse.core.internal.resources.Workspace.newResource(Workspace.java:1509) at org.eclipse.core.internal.localstore.UnifiedTree.createChildNodeFromFileSystem(UnifiedTree.java:240) at org.eclipse.core.internal.localstore.UnifiedTree.addChildren(UnifiedTree.java:126) at org.eclipse.core.internal.localstore.UnifiedTree.addNodeChildrenToQueue(UnifiedTree.java:204) at org.eclipse.core.internal.localstore.UnifiedTree.accept(UnifiedTree.java:76) at org.eclipse.core.internal.localstore.FileSystemResourceManager.refreshResource(FileSystemResourceManager.java:622) at org.eclipse.core.internal.localstore.FileSystemResourceManager.refresh(FileSystemResourceManager.java:609) at org.eclipse.core.internal.localstore.FileSystemResourceManager.refreshRoot(FileSystemResourceManager.java:653) at org.eclipse.core.internal.localstore.FileSystemResourceManager.refresh(FileSystemResourceManager.java:602) at org.eclipse.core.internal.resources.Resource.refreshLocal(Resource.java:1222) at org.eclipse.core.internal.resources.Workspace.open(Workspace.java:1608) (In reply to comment #18) Ok, created a new bug 96679 *** This bug has been marked as a duplicate of 86846 *** |