| Summary: | [launch] launching takes forever | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Jeff McAffer <jeffmcaffer> |
| Component: | Debug | Assignee: | JDT-Debug-Inbox <jdt-debug-inbox> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | darin.eclipse, Michael_Rennie, pawel.1.piech, remy.suen |
| Version: | 3.6 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Jeff McAffer
Is it possible that the launch was waiting for a build to complete, or that the launch triggered a build before launching? (based on preference settings). I don't think so. It was simply reading the .java files. AFAICT there was no building going on (i.e., no class file being read/written and no resources being copied). Nothing was happening in the workspace prior to launching. Of course, this does not happen all the time but when it does its basically fatal. Exiting (i.e., killing) eclipse and restarting seemed to address the issue. This also seems to point to building etc NOT being the issue. I'm not sure what would be reading .java files. Launch does search the workspace (relevant projects) for problem markers before launching in order to detect potentially problematic compilation errors: IMarker[] markers = proj.findMarkers(IMarker.PROBLEM, true, IResource.DEPTH_INFINITE); However, I don't this triggers reading of files. Testing in my workspace of ~70 bundles I have never encountered this. Closing as worksforme - Jeff, if the problem happens again please reopen. |