Community
Participate
Working Groups
The java process (javaw.exe) remains running after eclipse exits, resulting in the largest memory hog, thus slowing the system. Workaround is to terminate the process from the windows task manager. At such an eclipse termination dialog is invoked.
What build are you using? How are you launching Eclipse? What application are you running (the SDK?)? Ever since 3.3 M5 the eclipse executable has used JNI to launch Java. There should not be a javaw.exe process unless you use the -vm option.
I am seeing very similar behavior with Eclipse 3.3M7 under Windows XP SP2 with Java 1.5_11. I am launching eclipse by double clicking on the eclipse.exe that came in the release zip file. The process name that I see in the task manager is "eclipse.exe" Unlike the user in comment #1, when I click on "End Process" in the task manager I do not see an eclipse terminiation dialog. This doesn't happen 100% of the time when I close eclipse, but it does happen frequently (about 75%) of the time. When it does occur, the sequence is as follows: 1) Exit Eclipse 2) See Normal Eclipse termination dialog 3) Open Windows Task Manager and wait for a bit 4) See that "eclipse.exe" is present and consuming large amounts of memory. 5) Select eclipse.exe and click on "End Process" 6) Process goes away without any UI elements coming up.
Please produce a stack trace the next time you see this happen. See http://wiki.eclipse.org/index.php/How_to_report_a_deadlock for instructions. Thanks.
This works for me. The original report talks about a java process. In eclipse 3.3 the default behavior should be to use jni to launch java in process without a separate java process. For the issue in comment 2 if you see this again can you gather the stack trace information requested in comment 3 and reopen this bug? Thanks.
