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

Bug 356106

Summary:	VM exits with 139 exit value while running UI tests in workspace
Product:	[Eclipse Project] Platform	Reporter:	David Williams <david_williams>
Component:	UI	Assignee:	Platform-UI-Inbox <Platform-UI-Inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	daniel_megert, remy.suen
Version:	4.2
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:	stalebug

Description David Williams

2011-08-29 13:04:22 EDT

This ultimately is probably "not eclipse", and more likely a JIT bug, or similar, but wanted to document it here, in case we need to narrow down test case, or something. 

I have been trying to run UI Test Suite on Linux (Mint 11) using IBM's 64 bit VM (ibm-java-x86_64-60-SR9FP2) and in one case, the tests cause a "vm exit" on test number 960 (testMenuVisibilityWtihCustomFactory) with an exit code of 139. 

So, far, I've not been able to find any "hints" in the .metadata/.log, no snapshot dumps, etc. 

Running just that one test the error does not occur. Commenting out that test, the suite continues to run to completion. 

I've "googled" for "exit 139" and found a few things related to Mac VMs ... but, so far didn't see anything about Linux VMs. 

Running the test Suite in "debug mode" seems to cause the problem to occur in a different place, testActionSets, test number 759. 

Guess the first thing to try in debugging will be to turn off JIT and see if it still happens.

Comment 1 Remy Suen

2011-08-29 13:35:19 EDT

(In reply to comment #0)
> I have been trying to run UI Test Suite on Linux (Mint 11) using IBM's 64 bit
> VM (ibm-java-x86_64-60-SR9FP2) and in one case, the tests cause a "vm exit" on
> test number 960 (testMenuVisibilityWtihCustomFactory) with an exit code of 139.

Which class and project is this test method from?

Comment 2 David Williams

2011-08-29 14:40:52 EDT

(In reply to comment #1)
> (In reply to comment #0)
> > I have been trying to run UI Test Suite on Linux (Mint 11) using IBM's 64 bit
> > VM (ibm-java-x86_64-60-SR9FP2) and in one case, the tests cause a "vm exit" on
> > test number 960 (testMenuVisibilityWtihCustomFactory) with an exit code of 139.
> 
> Which class and project is this test method from?

MenuTest
org.eclipse.ui.tests.activities

Comment 3 David Williams

2011-08-29 16:00:52 EDT

FWIW, setting JAVA_COMPILER=nojit does cause the problem to go away. While that does not prove it is a jit problem, exactly, it would imply more investigation along that route would be warrented; see if a specific test case could be found, or a specific "no jit method" could be isolated. I've tracked these down before, and as I recall, it is not easy! :/

I'll also try on a more supported platform (I'm using Mint 11 at the moment ... I think I have a few Ubuntu 10.10 installs around somewhere).

Comment 4 David Williams

2011-08-29 22:08:49 EDT

I did try Mint 10 (based on Ubuntu 10.10) and the same problem occurs there. 

It may be more complicated than a JIT bug, though, because I see same problem running with the Sun/Oracle CM (version 6_27), though it exits with 139 at a different point ... test number 582 test 'testSelectReveal' in org.eclipse.ui.tests.navigator.ResourceNavigatorTest. 

I also tried running the 32 bit version (with 32 bit VM, on 32 bit OS) and the problem does not occur there (though, there were even more junit failures, when running "from the workbench"). 

So, complicated. Not sure where to go next.

Comment 5 Eric Moffatt

2011-10-11 15:57:11 EDT

...and I'm not sure where we can triage it...;-). Remy, any suggestions ?

Comment 6 Lars Vogel

2019-11-14 03:39:36 EST

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.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.