Bugzilla – Full Text Bug Listing
| Summary: | Eclipse hourglasses frequently for substantial times | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Reinhardt Christiansen <rhinosfl> |
| Component: | UI | Assignee: | Platform-UI-Inbox <Platform-UI-Inbox> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | remy.suen |
| Version: | 3.7.1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Reinhardt Christiansen
While it's busy, you can take a few stack traces to find out where the JVM thinks it is spending its time. See http://wiki.eclipse.org/index.php/How_to_report_a_deadlock for hints on taking snapshots. PW I think I've solved this bug at my end. I'm not sure if any followup action should be taken on your part. I'm sorry for the very lengthy delay in getting back to this! Between running virus and spyware scans, dealing with a lot of interruptions, and trying some of my own solutions to the problem, I seem to have resolved the issue on my own. The virus sweep revealed one virus, which I removed, and the spyware sweep came up clean but I don't think they were the issue. I _think_ the issue was with the Problems view and my compiler settings. My workspace has 78 projects in it, of various sizes and degrees of completion. Until the other day, I had always left both the Problems view and the compiler settings at their default settings. The number of errors and warnings was fairly low. The other day, I decided to change all the compiler settings that were set at "ignore" to "warning". After that, the number of items in the Problems view soared to over 80,000 items. Only about 150 of these were errors and most of the warnings were of a rather minor nature but there were a lot of them. I was working through specific projects to solve their problems and get totally clean compiles but couldn't see their messages so I examined the Problems View settings and disabled the 50,000 message limit for warnings. The onset of my hourglassing problem did not coincide PRECISELY with the changes to the compiler and Problem View settings but they were pretty close. That's why it wasn't immediately obvious what caused the hourglassing. I've left the compiler settings alone, i.e. every possible condition is either an error or a warning and none are ignored. However, I've gone into the Problems View and changed it so that it only reveals problems on the currently selected project rather than all projects. The performance of Eclipse is perfectly reasonable now and hourglassing is negligible. My working theory is that there was a LOT of background effort involved in redrawing the Problems View each time I fixed one of the errors and warnings and THAT was the source of the hourglassing. I had initially wondered if this might be the cause of the problem but dismissed it because I assumed that the Eclipse code was so robust that this would be trivial for it. But by reducing the scope of the Problems view, the hourglassing essentially went away so now I'm pretty sure that the background work done by Problems View was a lot more substantial than I had allowed for. I don't know what's going on in the background so perhaps you can tell me if that's a reasonable theory. Then again, I'm sure you're busy given the number of bugs I saw in Bugzilla so maybe you don't want to waste time on confirming my speculations. It's vaguely possible that the one virus I removed was the real culprit, not Eclipse at all. I can't say with certainty. If you want to close this on the grounds that the problem went away for the only (?) user who reported it, that's fine by me. I don't know if it would be worthwhile to include a caution on the Configure COntents page for the Problems View that allowing more than 'n' (where 'n' is perhaps the 50000 item default limit) errors and warnings in the Problems View may lead to a significant degradation in the overall performance of Eclipse. It might seem obvious to most people using Eclipse and therefore not be needed. It surprised me but I was probably just naive. Maybe the Problems View code could be reworked to make it more efficient so that even 80,000+ errors wouldn't degrade performance. But I'm not sure how often developers have that volume of messages. For all I know, most users only keep one project in each Workspace and have far fewer warnings, in which case reworking the Problems View would be a pretty low priority since it would help very few people. Anyway, unless you need something more from me, I'm going to consider this matter closed and let you close this bug with whatever status seems appropriate to you. My apologies if I've wasted anyone's time there. This has apparently already been addressed... |