Bug 37202 - GTK Exception on gtk_progress_bar_set_fraction
Summary: GTK Exception on gtk_progress_bar_set_fraction
Status: RESOLVED DUPLICATE of bug 31941
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 2.1   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Felipe Heidrich CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-05-04 17:11 EDT by Don Park CLA
Modified: 2003-07-07 15:24 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Don Park CLA 2003-05-04 17:11:47 EDT
I have Mandrake 9.1 and Java Sun 1.4.2(beta) installed on an athlon 1ghz desktop
and a pentium 3 mobile 850mhz laptop. On each system Eclipse will crash when I
try to do certain actions. One is to share a project with CVS. 

The error file on the desktop shows:
An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : 11 occurred at PC=0x4D9C57F4
Function=(null)+0x4D9C57F4
Library=/usr/lib/libgdk-x11-2.0.so.0
 
NOTE: We are unable to locate the function name symbol for the error
      just occurred. Please refer to release documentation for possible
      reason and solutions.
 
 
Current Java thread:
        at org.eclipse.swt.internal.gtk.OS.gtk_progress_bar_set_fraction(Native
Method)
        - locked <0x48b33c28> (a java.lang.Class)
        at org.eclipse.swt.widgets.ProgressBar.updateBar(ProgressBar.java:213)
        at org.eclipse.swt.widgets.ProgressBar.setSelection(ProgressBar.java:203)
        at
org.eclipse.jface.dialogs.ProgressIndicator.worked(ProgressIndicator.java:115)
 

So it appears to be an SWT/GTK issue. 

On the laptop Eclipse will crash during the exact same action, except the error
is a little different
Signal 8 in function (null)+0x4DC3F4C4 in library
/usr/lib/gtk-2.0/2.2.0/engines/libgalaxy.so

the top of the stack is
org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(Native Method)
Comment 1 Don Park CLA 2003-05-04 18:18:53 EDT
I downloaded M20030430 and the bug has disappeared.
Comment 2 Michael Lupp CLA 2003-06-22 06:23:17 EDT
Hi,

I had this bug with eclipse 2.2.1 RC1 and still with 2.2.1 RC2 (RedHat 9.0 with
gtk2-2.2.1-4). Here is a part of the debugging output while debuggig eclipse:

An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : 11 occurred at PC=0x4D838F15
Function=(null)+0x4D838F15
Library=/usr/lib/libgdk-x11-2.0.so.0

NOTE: We are unable to locate the function name symbol for the error
      just occurred. Please refer to release documentation for possible
      reason and solutions.


Current Java thread:
	at org.eclipse.swt.internal.gtk.OS.gtk_progress_bar_set_fraction(Native Method)
	- locked <0x486cefc0> (a java.lang.Class)
	at org.eclipse.swt.widgets.ProgressBar.updateBar(ProgressBar.java:213)
	at org.eclipse.swt.widgets.ProgressBar.setSelection(ProgressBar.java:203)
	at org.eclipse.jface.dialogs.ProgressIndicator.worked(ProgressIndicator.java:115)
	at
org.eclipse.jface.dialogs.ProgressMonitorDialog$ProgressMonitor.internalWorked(ProgressMonitorDialog.java:209)
Comment 3 Michael Lupp CLA 2003-06-26 02:43:16 EDT
Sorry, I forgot to reopen, while adding my last comment.
Comment 4 Steve Northover CLA 2003-06-26 17:23:00 EDT
Felipe, didn't we work around this bug in GTK?  Please check into this.  
Thanks.
Comment 5 Felipe Heidrich CLA 2003-06-26 17:37:54 EDT
The problem with the laptop is a bug with the Mandrake theme, just run eclipse 
using a different theme.

The problem with set_fraction was fixed a couple months ago, which version of 
eclipse are you running: 2.2.1 RC1 and 2.2.1 RC2 is not clear, you mean GTK 
2.2.1 and eclipse 2.1.1 RC1 and eclipse 2.1.1 RC2 ?

Michael, just get a new version of eclipse and give it a try.
Note: This bug was fixed in 2.1.1 stream as well, if you need to run 2.1.1 try 
eclipse 2.1.1 RC3, other you can get the last integration build.


*** This bug has been marked as a duplicate of 31941 ***
Comment 6 Michael Lupp CLA 2003-07-04 10:11:34 EDT
This error is still in 2.1.1 RC4 (tested with RedHat 9.0 with gtk2-2.2.1-4). But
it seems to work in 3.0 M1.
Comment 7 Felipe Heidrich CLA 2003-07-04 11:38:32 EDT
works fine for me, which theme are you using?
Comment 8 Michael Lupp CLA 2003-07-07 15:24:24 EDT
I've been using the redhat default theme (Bluecurve).