Comment 1 antoni aloy 2005-11-16 16:13:20 EST

Created attachment 30099 [details]
gpf dump

find attached a gpf dump sample

Comment 2 Dani Megert 2005-11-17 04:19:17 EST

Happens during an OS call made by SWT

Comment 3 Billy Biggs 2005-11-17 08:52:57 EST

What version of GTK+ do you have installed?

Comment 4 antoni aloy 2005-11-17 13:26:54 EST

(In reply to comment #3)
> What version of GTK+ do you have installed?
I have the one which comes with the lastest release of Ubuntu,gtk+2 I think,
Before Ubuntu I had FC4 wich had the same problem.

Comment 5 Billy Biggs 2005-11-17 14:01:39 EST

In ubuntu, use "dpkg -l | grep libgtk2.0" to see what specific version is in use.

From your log, you are on a Linux/PPC machine and using the IBM Java 5.0 JRE. 
Bug 111305 is another log of a crash with this VM.  Can you try with an IBM
1.4.2 VM for this architecture?  You said it also crashed under FC4, was this
with the same VM (also Java 5)?

The other interesting thing about your crash is that it occurs in an input method:

org/eclipse/swt/internal/gtk/OS._gtk_im_context_filter_keypress(Native Method)
org/eclipse/swt/internal/gtk/OS.gtk_im_context_filter_keypress(OS.java:4505)
org/eclipse/swt/widgets/Control.filterKey(Control.java:1445)
org/eclipse/swt/widgets/Control.gtk_key_press_event(Control.java:1975)
org/eclipse/swt/widgets/Composite.gtk_key_press_event(Composite.java:566)

Are you using the default GTK+ IME or are you using a different input method module?

Comment 6 antoni aloy 2005-11-17 14:11:29 EST

(In reply to comment #5)
> In ubuntu, use "dpkg -l | grep libgtk2.0" to see what specific version is in use.
> 
Here you have:

ii  libgtk2.0-0                        2.8.6-0ubuntu2.1             

> From your log, you are on a Linux/PPC machine and using the IBM Java 5.0 JRE. 
> Bug 111305 is another log of a crash with this VM.  Can you try with an IBM
> 1.4.2 VM for this architecture?  You said it also crashed under FC4, was this
> with the same VM (also Java 5)?
Before that I used Eclipse 3.1 with 1.4.2 with the same problems as before. On
FC4 I had 1.4.2 in fact, so in my oppinion it's not a problem with the VM.


> 
> The other interesting thing about your crash is that it occurs in an input method:
> 
> org/eclipse/swt/internal/gtk/OS._gtk_im_context_filter_keypress(Native Method)
> org/eclipse/swt/internal/gtk/OS.gtk_im_context_filter_keypress(OS.java:4505)
> org/eclipse/swt/widgets/Control.filterKey(Control.java:1445)
> org/eclipse/swt/widgets/Control.gtk_key_press_event(Control.java:1975)
> org/eclipse/swt/widgets/Composite.gtk_key_press_event(Composite.java:566)
> 
> Are you using the default GTK+ IME or are you using a different input method
module?
What? Sorry I don't understand what do you mean.

Comment 7 Billy Biggs 2005-11-17 14:18:49 EST

Do you have any crash logs from when you were running on FC4?

As for the input method, in any GTK+ text editor or edit box, right click and
look under the menu "input methods".  If you have chosen an alternate keyboard
input layout then it may not be on "default".  Depending on what kind of
keyboard you have and what you have configured in your preferences, you may be
using an alternate input scheme to be able to type accented characters etc.

Comment 8 antoni aloy 2005-11-17 14:23:26 EST

(In reply to comment #7)
> Do you have any crash logs from when you were running on FC4?
> 
No sorry!

> As for the input method, in any GTK+ text editor or edit box, right click and
> look under the menu "input methods".  If you have chosen an alternate keyboard
> input layout then it may not be on "default".  Depending on what kind of
> keyboard you have and what you have configured in your preferences, you may be
> using an alternate input scheme to be able to type accented characters etc.
OK
I have the Cedilla input method. This should be my default as I haven't choosed it.

Now I'm trying to reproduce the bug on JDK 1.4.2 ...
--
Toni

Comment 9 Billy Biggs 2005-11-17 14:26:33 EST

Please also try with different input methods.

Comment 10 Jason Brittain 2005-12-02 19:26:58 EST

> Do you have any crash logs from when you were running on FC4?

I have those, because I'm seeing this same crash, and it's preventing me from
using Eclipse, at least with the IBM 1.5.0 beta JDK.  Eclipse starts (slowly),
then when it comes all the way up, I open a file to edit, then I use the mouse
to put the cursor where I want to type some content, and the very first key I
press causes the crash.

My machine is a PowerBook G4 running Fedora Core 4 PPC.  I have updated my
kernel to 2.6.14.  I can run any commands you'd like to help diagnose.  Just
ask.

Shouldn't this bug be a P1?  Or, is it lower priority only because this
particular JDK is still a beta?

I will attach the javacore log file next.

Comment 11 Jason Brittain 2005-12-02 19:32:08 EST

Created attachment 31089 [details]
Crash dump on Fedora Core 4 of IBM JDK 1.5.0 beta.

This is a crash of 3.2M3, but the same thing happens with v3.1 (release) or
v3.1.1 (release) with IBM JDK 1.5.0 beta on Fedora Core 4.

Comment 12 Jason Brittain 2005-12-02 19:41:14 EST

I am also trying IBM JDK 1.4.2 on FC4 PPC.  Today, I cannot reproduct this bug.
I did try this before, and I'm pretty sure I was able to reproduce it that way,
but I can't at the moment.

Also, this bug seems intermittent.  Sometimes when I run Eclipse on IBM JDK 1.5.0
beta, I can edit files.  Then later, while it is still running, it crashes like
this, and when I restart it I can't edit files at all -- the first character I
type into the editor crashes it.

About which gtk I have, here is some info that may help:

# rpm -q gtk2
gtk2-2.6.10-2

# ls /usr/lib/libgtk*
/usr/lib/libgtk-1.2.so.0
/usr/lib/libgtk-1.2.so.0.9.1
/usr/lib/libgtkhtml-2.so.0
/usr/lib/libgtkhtml-2.so.0.0.0
/usr/lib/libgtkhtml-3.6.so.18
/usr/lib/libgtkhtml-3.6.so.18.0.2
/usr/lib/libgtkmathview_custom_reader.so.0
/usr/lib/libgtkmathview_custom_reader.so.0.7.5
/usr/lib/libgtkmathview_libxml2_reader.so.0
/usr/lib/libgtkmathview_libxml2_reader.so.0.7.5
/usr/lib/libgtkmathview_libxml2.so.0
/usr/lib/libgtkmathview_libxml2.so.0.7.5
/usr/lib/libgtksourceview-1.0.so.0
/usr/lib/libgtksourceview-1.0.so.0.0.0
/usr/lib/libgtkspell.so.0
/usr/lib/libgtkspell.so.0.0.0
/usr/lib/libgtk-x11-2.0.so
/usr/lib/libgtk-x11-2.0.so.0
/usr/lib/libgtk-x11-2.0.so.0.600.10

Comment 13 Billy Biggs 2005-12-03 01:28:12 EST

Stephan, have you ever seen this crash before?

Comment 14 Stephan Michels 2005-12-03 06:09:16 EST

Created attachment 31093 [details]
Crash log

Yes, the crash comes only at editing java code. If I save it then I get the crash like in bug 111305.

Comment 15 Jason Brittain 2005-12-05 00:20:22 EST

Just to see what would happen, I built Eclipse 3.2M3 from source on my
Fedora Core 4 powerbook (the same one where I saw the crash in the first
place).  I built it with the IBM 1.5.0 beta JDK -- I had to set AWT_LIB_PATH
like this:

# export AWT_LIB_PATH=/opt/IBMJava2-ppc-142/jre/bin

Then I built Eclipse like this (as per the directions):

# ./build -os linux -ws gtk -arch ppc -compilelibs

After tinkering with a build problem with the launchertmp/library/gtk path,
I was able to get it to build successfully, and then I unpacked and ran it
and tested this bug again.  Same thing.  It crashes in the editor, with the
same stack trace.

I played with it some more and found that if I typed very slowly (wait for
all IDE activity to stop by watching a CPU load monitor, then typing at most
one character per second or two), I could type somewhere around 8 characters
or so into the editor before it crashes.  Typing any faster makes it crash
earlier, or not waiting until all CPU activity stops before typing also
makes it crash right away.  This is how it behaves in both the pre-compiled
binary I downloaded from eclipse.org, and also the one I built from source.

Comment 16 Jason Brittain 2005-12-09 12:32:09 EST

Update:

This week sometime IBM has released their JDK 1.5.0 GA.  I just downloaded it
and tried Eclipse again.  It crashes in exactly the same way it did when I ran
it on the IBM 1.5.0 beta.  Also, I see that the file contents of these two
different versions of the IBM 1.5.0 are different, so there were changes, but
apparently nothing that fixes this bug.  I have not tried to recompile Eclipse
from source with the GA release, however (I'm not sure that would matter).

Comment 17 Jason Brittain 2005-12-16 16:24:09 EST

Since this bug prevents anyone from using Eclipse on 32-bit PPC Linux with
the only implementation (IBM) of Java 1.5 for the platform, can we change the
priority of this bug at least to P2?

Comment 18 Stephan Michels 2005-12-26 15:53:08 EST

The problem doesn't occur for me any longer with the 1.5 GA version. Seems to be fixed in this version and I think the bug can closed from my POV.

Comment 19 Jason Brittain 2005-12-31 03:37:31 EST

I just tried it again with IBM JDK 1.5.0 GA running Eclipse 3.2M4, and it
crashes exactly the same way.

Comment 20 Billy Biggs 2005-12-31 09:48:24 EST

Jason, your crash is also in the input method handler.  Which input method are you using?

I tried to reproduce this crash on our Linux-PPC machine using the 5.0 GA VM and so far have not been able to.

Comment 21 Jason Brittain 2005-12-31 15:00:31 EST

Earlier, when I was trying 3.2M3 I tried at least a few different input
methods, including "Default", and they all acted the same.  I just checked
which input method I had selected for 3.2M4, and it's "Default".  I also
tried the "X Input Method" and that doesn't work either.

Comment 22 antoni aloy 2005-12-31 16:18:17 EST

I agree with Jason. I have the same effect on 3.2 and it doesn't matter the input type or the virtual machine.
I have this issue either on IBM JDK 1.4.2 or JDK 1.5 with a Ubuntu Linux. I have also observed another effect: the 3.2 version on PPC get lots of memory compared with the i386 version given the default configuration.

This bug makes Eclipse for PPC unusable for me. :(

Comment 23 Stephan Michels 2006-01-02 04:00:34 EST

Created attachment 32388 [details]
Configuration details

I added my configuration details as a file. Maybe you can compare it with your configurations to see if there is a difference that can explain why it works for 
me and not for you. And please ensure you use the same "java.fullversion". And as a side note, I use an up-to-date version of Ubuntu Dapper.

Comment 24 Jason Brittain 2006-01-02 17:18:44 EST

Your configuration info got me farther.  I noticed that in your configuration,
you disregarded the configuration instructions given on the download page that
say that you should set "-vmargs -Dosgi.locking=none".  You don't have that set.
I always had it set (I do try to follow directions :).  Once I removed that,
my startup command looks like this:

$ /home/jbrittain/eclipse-3.2M4/eclipse -clean -vm /opt/ibm/java2-ppc-50/bin/java

When I run it like that, I no longer get the crash that I reported earlier.
I can type into the editor, and the characters now show up, and after a few
seconds the CPU goes idle again and I can continue to type.  So, I can now
edit Java code.  I also checked that my config's "java.fullversion" is
exactly the same as yours.  Few other things look different when I diff the
config sets.

BUT: Now I get a different crash..

When I edit for a bit, then switch desktop pages to where my Mozilla is, use
the web a little, then switch back to the desktop page where Eclipse is,
Eclipse crashes after several seconds of trying to repaint the window.  It
appears I can reproduce this bug frequently, but not quite every time.

Shall I file this as a separate bug?  It's a different stack trace -- yet
another SWT native code crash.  (Wasn't this one of the problems Java existed
to prevent in the first place?)

I will attach the javacore text file..

Comment 25 Jason Brittain 2006-01-02 17:22:25 EST

Created attachment 32394 [details]
SWT crash on linux ppc when switching desktop pages.

Comment 26 Greg Watson 2006-03-28 13:11:50 EST

Created attachment 37115 [details]
crash as soon as character is typed in C/C++ editor

I get the same error as soon as I type a character in the C/C++ editor. It appears to be completely reproducable. I see the error with or without the -vmargs -Dosgi.locking=none options.

I'm using IBM JRE 5.0 on a Yellow Dog 4.1 system (a ppc machine.) The GTK2 package version reported by RPM is gtk2-2.8.6-3.

Comment 27 Steve Northover 2006-08-02 14:39:31 EDT

*** Bug 152323 has been marked as a duplicate of this bug. ***

Comment 28 Eduardo Trápani 2006-08-31 13:55:09 EDT

Same problem, sometimes I get the error with the first keypress, sometimes later on.  Maybe copying/pasting or backspacing makes it happen quicker.  I'm using the default input method and I've tried more than one theme, nothing helps ...

This renders the program almost unusable under ppc.

I've tried with IBM JVM 1.4.2, same result.  I upgraded gtk+ (now at 2.8.18 from 2.6.4) and glib2.0 (now at 2.10.2 from 2.6.4) but still I get the same error.

I using Debian stable/testing.

Is there anything I could try to get rid of this bug?  I'm running the rails plugin, if that matters and the command line is: JAVA_HIGH_ZIPFDS=500  ./eclipse -clean (and sometimes -debug to try to tackle the problem)  Without the JAVA_HIGH... I still get the gpf.

0SECTION       GPINFO subcomponent dump routine
NULL           ================================
2XHOSLEVEL     OS Level         : Linux 2.6.16-rc1
2XHCPUS        Processors -
3XHCPUARCH       Architecture   : ppc
3XHNUMCPUS       How Many       : 1
NULL
1XHEXCPCODE    J9Generic_Signal_Number: 00000004
1XHEXCPCODE    Signal_Number: 0000000B
1XHEXCPCODE    Error_Value: 00000000
1XHEXCPCODE    Signal_Code: 00000001
1XHEXCPCODE    Handler1: 0FB032C0
1XHEXCPCODE    Handler2: 0FA65920
NULL
1XHEXCPMODULE  Module: /usr/lib/libgobject-2.0.so.0
1XHEXCPMODULE  Module_base_address: 0E83B000


0SECTION       ENVINFO subcomponent dump routine
NULL           =================================
1CIJAVAVERSION J2RE 5.0 IBM J9 2.3 Linux ppc-32 build j9vmxp3223-20060504
1CIVMVERSION   VM build 20060501_06428_bHdSMR
1CIJITVERSION  JIT enabled - 20060428_1800_r8
1CIRUNNINGAS   Running as a standalone JVM
1CICMDLINE     /usr/bin/java -Xms40m -Xmx256m -jar /home/edu/progs/eclipse/./sta
rtup.jar -os linux -ws gtk -arch ppc -launcher /home/edu/progs/eclipse/./eclipse
 -name Eclipse -showsplash 600 -exitdata 178006 -clean -debug -vm /usr/bin/java
-vmargs -Xms40m -Xmx256m -jar /home/edu/progs/eclipse/./startup.jar
1CIJAVAHOMEDIR Java Home Dir:   /usr/lib/j2sdk1.5-ibm/jre
1CIJAVADLLDIR  Java DLL Dir:    /usr/lib/j2sdk1.5-ibm/jre/bin
1CISYSCP       Sys Classpath:   /usr/lib/j2sdk1.5-ibm/jre/lib/vm.jar;/usr/lib/j2
sdk1.5-ibm/jre/lib/core.jar;/usr/lib/j2sdk1.5-ibm/jre/lib/charsets.jar;/usr/lib/
j2sdk1.5-ibm/jre/lib/graphics.jar;/usr/lib/j2sdk1.5-ibm/jre/lib/security.jar;/us
r/lib/j2sdk1.5-ibm/jre/lib/ibmpkcs.jar;/usr/lib/j2sdk1.5-ibm/jre/lib/ibmorb.jar;
/usr/lib/j2sdk1.5-ibm/jre/lib/ibmcfw.jar;/usr/lib/j2sdk1.5-ibm/jre/lib/ibmorbapi
.jar;/usr/lib/j2sdk1.5-ibm/jre/lib/ibmjcefw.jar;/usr/lib/j2sdk1.5-ibm/jre/lib/ib
mjgssprovider.jar;/usr/lib/j2sdk1.5-ibm/jre/lib/ibmjsseprovider2.jar;/usr/lib/j2
sdk1.5-ibm/jre/lib/ibmjaaslm.jar;/usr/lib/j2sdk1.5-ibm/jre/lib/ibmcertpathprovid
er.jar;/usr/lib/j2sdk1.5-ibm/jre/lib/server.jar;/usr/lib/j2sdk1.5-ibm/jre/lib/xm
l.jar;
1CIUSERARGS    UserArgs:
2CIUSERARG               -Xjcl:jclscar_23
2CIUSERARG               -Dcom.ibm.oti.vm.bootstrap.library.path=/usr/lib/j2sdk1
.5-ibm/jre/bin
2CIUSERARG               -Dsun.boot.library.path=/usr/lib/j2sdk1.5-ibm/jre/bin
2CIUSERARG               -Djava.library.path=/usr/lib/j2sdk1.5-ibm/jre/bin:/usr/
lib/j2sdk1.5-ibm/jre/bin/j9vm:/usr/lib/j2sdk1.5-ibm/jre/bin:/usr/lib/mozilla:/us
r/lib
2CIUSERARG               -Djava.home=/usr/lib/j2sdk1.5-ibm/jre
2CIUSERARG               -Djava.ext.dirs=/usr/lib/j2sdk1.5-ibm/jre/lib/ext
2CIUSERARG               -Duser.dir=/home/edu/progs/eclipse
2CIUSERARG               _j2se_j9
2CIUSERARG               vfprintf 0x10003F10
2CIUSERARG               -Xms40m
2CIUSERARG               -Xmx256m
2CIUSERARG               -Dinvokedviajava
2CIUSERARG               -Djava.class.path=/home/edu/progs/eclipse/./startup.jar
2CIUSERARG               vfprintf
2CIUSERARG               _port_library 0x0FDC3F20
2CIUSERARG               -Xdump

Comment 29 Eduardo Trápani 2006-09-06 09:38:53 EDT

Adding osgi.locking=none to configuration/config.ini seemed to make it a little more stable, but not much.  By the way, I cannot found any reference to that in the documentation.

In the hope that it will help find the bug let me tell you that once I get the gpf I have only two ways to be able to start working again:

a) kill the X server (it's a bit of an overkill but sometimes it works)

b) completely erase (rm -rf) the directories configuration/configuration/org.eclipse.osgi/ configuration/org.eclipse.core.runtime/  They are recreated.  That gives me some more time of work until the next gpf.  That seems to work everytime.

If I don't take one of those steps I will always get the gpf at the first keypress.

And definitely, copy/pasting (^C/^V) makes the problem worse.  But X highlighting and middle-button copying seems to work ok.

Comment 30 Bogdan Gheorghe 2007-05-08 16:46:31 EDT

*** Bug 176942 has been marked as a duplicate of this bug. ***

Comment 31 Kevin Barnes 2007-05-10 12:35:53 EDT

I was able to reproduce this bug with the java 5 vm, however since running with the '-Xnojit' vm argument I have not crashed. Has anyone else tried this vm arg?

Comment 32 Kevin Barnes 2007-05-10 14:08:36 EDT

Also note that I've never crashed running the 1.4.2 vm, nor have I crashed using the early access Java 6 vm that is now available. 

Comment 33 Kevin Barnes 2007-05-11 09:02:02 EDT

Since this appears to be a VM bug, I'm marking it as WORKSFORME. 
Note that a warning about the IBM Java 5 VM has been added to the click through for the Linux-PPC build on the Eclipse download page. 

Comment 34 Jason Brittain 2007-05-11 15:48:18 EDT

I can't find any note of this on the download pages.  Plus, the Eclipse
Reference Platforms on this page:

http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_2.html#TargetOperatingEnvironments

Shows that the IBM JVM is the only officially suggested JVM for PPC Linux,
while showing nothing about this bug.  It even lists the exact version of
the IBM JVM that this bug is reported against.

I cannot test newer PPC Linux JVMs since I no longer have a PPC machine to
try it on (believe me, I'm happier).  But, unless you're testing on Fedora,
Ubuntu, or Yellow Dog as the bug was reported on, then you can't see if it
works or not.  Kevin: which distro/version did you test on?

Also, since this bug has had no attention for about a year, it's possible
that it's no longer valid for modern versions of these distros.  But, at
least the docs should say that Eclipse may not run on the versions of the
IBM JVM we reported this bug against.

Comment 35 Kevin Barnes 2007-05-11 16:02:47 EDT

We tested on Yellowdog 4.1 which is the only PPC-linux machine that we have access to.

The following text was added to the "Important Notes" click through page for future builds (starting with I20070511-0010). Every user sees this page before they can download the Linux-PPC build. 




When running on the IBM Java 5.0 VM, Eclipse crashes while the user is typing in an editor. If using this VM you must disable the JIT
 with the -Xnojit vm argument to avoid the crashes (https://bugs.eclipse.org/bugs/show_bug.cgi?id=116730). The command line for launching Eclipse with this vm should be: 
"eclipse -vmargs -Dosgi.locking=none -Xnojit"

Comment 36 Kevin Barnes 2007-05-11 16:21:07 EDT

I'll also point out that all of the attached crash logs are for the 1.5.0 vm and we have not been able to reproduce the crash on the 1.4.2 vm. 

The reference platform for PPC is 1.4.2 (according to the 3.2 final plan linked above, and the 3.3 draft play here http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_3.html#TargetOperatingEnvironments)