Community
Participate
Working Groups
there have been similar bugs along these lines, but the ones that seem relevant have been closed or just died. With both 3.0M4 and 3.0M5, after installing the examples and opening a jsp with the JSP editor (and not before these actions), the CPU % of the machine goes to 100 and stays there, even if Eclipse isn't the main app, even if iconified, etc. The scary part is that closing the jsp doesn't fix it - whatever background thread is causing it continues to run. CPU doesn't come back down until the workbench is restarted. Eclipse is running like it does by default (with a javaw.exe) on this Win2K box, so I'm not sure how to get a thread dump of Eclipse's own threads to report. I've seen bug reports that talk about CTRL+BREAK in a java console, but since this is javaw.exe instead of java.exe, there's no java console available, at least not that I can see in the system tray. Thanks!
You're not talking about a deadlock, right? Can you provide the steps e.g. do you install the examples into a fresh workspace?
fresh install, install examples, restart workbench once they're installed, create a cvs server entry, fetch the project, open jsp. No deadlock at all - CPU % goes up to 100 and stays there, but everything still "works" fine. Close the jsp editor, CPU % stays at 100. Instructions on how to dump the threads under Windows and the javaw.exe would be great if they're available :)
What version of Eclipse are you using for the latest test? Would it be possible to attach the jsp file that triggers the problem? You can create a full thread dump by pressing Control-Break in the console window.
waiting for user input
Get rid of deprecated state.
.
