Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 314802

Summary: vm crash dump on exit, first time
Product: [Eclipse Project] Equinox Reporter: David Williams <david_williams>
Component: FrameworkAssignee: equinox.framework-inbox <equinox.framework-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: mknauer, pawel.pogorzelski1, remy.suen, Szymon.Brandys
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard: stalebug
Attachments:
Description Flags
dump from Java EE IDE test
none
dump from JS IDE test none

Description David Williams CLA 2010-05-28 01:12:41 EDT
Created attachment 170295 [details]
dump from Java EE IDE test

Windows 7, 64 bit
IBM VM 6 SR 8

With the RC2 packages (JavaScript and Java EE IDE) after the first time I brought up the IDE, when I shut down, my VM "crashed" with attached dumps. 

First seen with JavaScript package, I was just going to skip reporting it, since I could not reproduce, but then found it happened with Java EE IDE also, exactly the first time, and then could not reproduce there, either. 

I'll try some others, but wanted to capture these dump/traces in bugzilla.
Comment 1 David Williams CLA 2010-05-28 01:14:10 EDT
Created attachment 170296 [details]
dump from JS IDE test
Comment 2 Markus Knauer CLA 2010-05-28 01:19:47 EDT
Does the Eclipse Platform SDK show the same problem or is this related to the packages only?
Comment 3 David Williams CLA 2010-05-28 01:37:57 EDT
Probably not platform sdk. Didn't try that, but tried 2 or 3 other packages and 
I could not reproduce, I tried Java (package), CPP, and also reinstalled Java IDE package, and none "crashed" on exit. 

I didn't do much much during the first two tests (where I saw the error) so I'm guessing just bad luck :) rather than some particular menu option. I tried 'help', running on server, etc., to try and reproduce, but didn't see crash on exit again.  

So ... not sure what to do with this bug. No reason to hold anything up. 
The only "eclipse things" I see in the dumps is "osgi console" (in both) and the data collector, in one.
Comment 4 David Williams CLA 2010-06-02 13:26:41 EDT
I'm moving this to Platform core resources, since the only thing I see in these dumps is I/O related. 

But, I can't read these dumps very well, so not sure what they say. 

Since I can't even reproduce them, feel free to close as "worksforme". 

I just wanted to be sure someone from platform saw them. 

Could be the VM or something, naturally. Like I said earlier, I wasn't even going to report it, except it happened twice, both times on the very first use and exit.
Comment 5 Szymon Brandys CLA 2010-06-07 11:28:12 EDT
The crash happens very late during Eclipse shutdown. It seems to be caused by System.exit(result) call in org.eclipse.equinox.launcher.Main#main line 1391. 

Tests show that during a proper shutdown, at this point we should see only the main and OSGi console threads running + some native threads. While in the attached dumps there are more, like "MultiThreadedHttpConnectionManager cleanup" thread. None of this thread calls core.resources methods though.
Comment 6 Eclipse Webmaster CLA 2019-09-06 16:07:29 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
Comment 7 Eclipse Genie CLA 2021-09-03 03:16:01 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.