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

Bug 130840

Summary: crash - g_main_context_iteration() - When Running JUnit Twice, Eclipse Crashes
Product: [Eclipse Project] Platform Reporter: Stu Statman <gurustu>
Component: SWTAssignee: Bogdan Gheorghe <gheorghe>
Status: RESOLVED WORKSFORME QA Contact:
Severity: major    
Priority: P3 CC: akurtakov, billy.biggs, daniel_megert, donal.duane, gurustu, mober.at+eclipse, snorthov
Version: 3.1.2   
Target Milestone: ---   
Hardware: PC   
OS: Linux-GTK   
Whiteboard:
Attachments:
Description Flags
Error Log none

Description Stu Statman CLA 2006-03-07 20:33:56 EST 
Thought this is an Eclipse crash, I am putting this bug under WTP, because it does not happen unless WTP is installed.

The repro case is fairly straightforward : I can run a collection of JUnit test cases once. Rarely (less than one time in ten) I can run them a second time. However, in the vast majority of cases, I cannot run them a second time without a full crash of Eclipse, with no log messages generated to .log.

I am running wtp-all-in-one-sdk-R-1.0.1-200602171228-linux-gtk.tar, but this also happens when I use the Eclipse software updates tool to install WTP over a straight Eclipse install.

The following message is generated to stdout :

#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
#  SIGSEGV (0xb) at pc=0xaa893c77, pid=5169, tid=16384
#
# Java VM: Java HotSpot(TM) Client VM (1.5.0_05-b05 mixed mode)
# Problematic frame:
# C  [libgtk-x11-2.0.so.0+0x1a0c77]
#
# An error report file with more information is saved as hs_err_pid5169.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
#

I will attach the error file.
Comment 1 Stu Statman CLA 2006-03-07 20:35:20 EST 
Created attachment 35881 [details]
Error Log
Comment 2 Stu Statman CLA 2006-03-07 20:35:53 EST 
Oh, also, I was able to reproduce this bug with Sun's 1.4.2_04 JDK.
Comment 3 Stu Statman CLA 2006-03-07 21:42:23 EST 
Further testing indicates that this is not WTP; the move to WTP must have been accompanied by a move to 3.1.2. That build, without WTP, also has the crash after two junit runs.
Comment 4 Arthur Ryman CLA 2006-03-08 13:30:27 EST 
Stu, yes WTP 1.0.1 is based on Eclipse 3.1.2.
Comment 5 Martin Aeschlimann CLA 2006-03-12 17:53:11 EST 
A VM dump is most likly a VM problem. But I move this bug to SWT, as they might be interested in the trace.
Comment 6 Billy Biggs CLA 2006-03-12 18:02:46 EST 
Not a VM problem, but a bug in either GTK+ or SWT.

Note that the user is running with GTK+ 2.2.1.
Comment 7 Martin Oberhuber CLA 2008-03-04 12:22:33 EST 
I've seen a similar crash with Eclipse 3.4M5 on 

Linux RHEL 4 (Nahant Update 3),
Sun Java 1.6.0_01-b03,
gtk2-2.4.13-18,
gtk+-1.2.10-33
/usr/lib/libgtk-x11-2.0.so.0.400.13

That GTK version should be fine according to the 3.4 Project plan (which requires GTK+ 2.2.1). See bug 181563 comment 18 for details. I reproduced the crash twice, but after a machine reboot I cannot reproduce it any more. Perhaps it's related to some stuff on the Clipboard or other current state of GTK.
Comment 8 Donal Duane CLA 2013-03-26 09:38:46 EDT 
Hi - is this addressed in any particualr release of GTK?
Comment 9 Alexander Kurtakov CLA 2014-02-18 15:00:29 EST 
SWT now requires GTK 2.10 can someone still reproduce it ?
Comment 10 Alexander Kurtakov CLA 2016-06-30 10:54:37 EDT 
More than 2 years without reply. Closing as can't reproduce it anymore. Please reopen if you can still reproduce it with supported version.