Comment 1 Claude Knaus 2002-10-16 04:23:52 EDT

Created attachment 2193 [details]
javacore dump

Comment 2 Steve Northover 2002-10-16 08:44:53 EDT

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

Comment 3 Veronika Irvine 2002-10-16 08:59:58 EDT

Did you see the following warning in the xterm from which you launched eclipse:

***WARNING: Gtk+ version too old (micro mismatch)

You must have GTK 2.0.1 or later.

What version of GTK are you using?  What type and version of linux are you
using?  We tried it on RedHat 7.2 with GTK 2.0.6 and Redhat 8.0 with GTK 2.0.6
and did not get an error.  Tried it on RedHat 7.2 with GTK 2.0.0 and got a
javacore on exit.

Comment 4 Claude Knaus 2002-10-16 09:29:30 EDT

typo: it's linux-gtk

Nope, I didn't see this message. I'm using GTK 2.0.2, RedHat 7.1.

Comment 5 Steve Northover 2002-10-16 12:36:57 EDT

We have temporarily backed out the new Tree and Table code.  The GP doesn't 
happen on GTK 2.0.5.  We are investigating.  It may be that we require users to 
upgrade.

Comment 6 Claude Knaus 2002-10-17 03:57:59 EDT

verified that with 20021016, the core dump is gone.

Comment 7 Tod Creasey 2002-10-17 10:49:48 EDT

Also verified on my machine

Comment 8 Silenio Quarti 2002-10-22 15:23:25 EDT

The new implementation of Tree and Table is out again (build 20021022 and
later). This particulary GPF has been fixed.

Note: there is another outstanding GPF. Check Bug#25212 for more
info.

Comment 9 Claude Knaus 2002-10-23 04:16:50 EDT

I-20021022 linux-gtk:

I don't get the old java core dump, instead I get a new one 
(gtk_tree_store_remove).
This only happened with my workspace. If I start up a fresh workspace, it works
fine.

Is this a SWT or a GTK bug? Although tempting to upgrade, I'm still resisting 
to stay on GTK 2.0.2 unless it's for certain that it's a GTK bug.

Attachment will follow.

Comment 10 Claude Knaus 2002-10-23 04:17:57 EDT

Created attachment 2254 [details]
java core dump

Comment 11 Claude Knaus 2002-10-23 04:54:41 EDT

Note: I removed the synchronized view (with I-20021018) and eclipse came up 
with 20021022. Now I readded the synchronize view to the perspective again
and it works fine for now.
Is it possible that this a varation of 25212 I'm seeing?

Comment 12 Silenio Quarti 2002-10-23 17:26:52 EDT

Claus,

The GPF of Bug#25212 has a different stack trace than this one, but it happens
in the same in same view. So it might be related. I am not sure about that,
since I have not been able to reproduce this problem yet.

The Bug#25212 is fixed, please could you try the latest SWT (HEAD) and see
if the problem still happens.

Thanks!
Silenio

Comment 13 Claude Knaus 2002-10-24 03:28:27 EDT

Reopened #25212. It's Claude, BTW :-)

Comment 14 Claude Knaus 2002-10-31 06:00:31 EST

It still happens with 20021030.

Comment 15 Grant Gayed 2002-10-31 10:40:26 EST

Cannot reproduce with 1031 Eclipse build on RH 7.3.  Tried gtk 2.0.0, 2.0.1, 
2.0.2 and 2.0.5.  Will seek out RH7.1 machine.

Comment 16 Claude Knaus 2002-10-31 12:13:49 EST

It didn't happen on launch. But I was manipulationg with the Synchornize View. 
Not sure any more what I did. Now it's running again... the javacore looked 
similar to the one I attached before on 1023 (same method failing).

Comment 17 Grant Gayed 2002-11-06 16:23:11 EST

okay, I finally have steps to reproduce this second GP.  Note that it only 
happens with gtk-2.0.2, not with gtk-2.0.5.

- change a resource that has been checked out of a repository
- select it, right-click -> Team -> Synchronize Outgoing Changes...
- double click it in the Sync view's tree so that a Comparison is shown
- click the "Incoming Mode" toolbar button
- GP happens

Comment 18 Claude Knaus 2002-12-05 04:55:45 EST

I-20021204 linux-gtk:

I just upgraded to gtk-2.0.5-1 and I still get it.
I got a crash in gtk_tree_store_remove() when the package explorer was visible.

How I worked around:

1) Start with motif.
2) Removed package explorer from perspective and readded it again.
3) Cover package explorer with some other view (junit) such that the whole
   perspective shows no tree views.
4) Shutdown and restart with gtk.
5) Bring package explorer to the front.
6) Shutdown and restart with gtk. -> comes up normally.

I don't know if it was 2) or 3) which fixed the problem (I suspect 2)).

Comment 19 Grant Gayed 2002-12-16 16:30:27 EST

I still can't replicate this with gtk 2.0.6, but the following snippet shows 
the problem with gtk 2.0.2, so I'll just go from here.  When the snippet is 
run, expand the first two levels of children and select the third, then press 
Dispose.  The expansion state of the nodes seems to be the determining factor.

public class TreeGtkGP {
	public static void main(String[] args) {
		Display display = new Display();
		Shell shell = new Shell(display);
		shell.setBounds(10, 10, 300, 300);
		Tree tree = new Tree(shell, SWT.NONE);
		tree.setBounds(10, 10, 240, 240);
		final TreeItem root = new TreeItem(tree, SWT.NONE);
		TreeItem i1 = new TreeItem(root, SWT.NONE);
		TreeItem i2 = new TreeItem(i1, SWT.NONE);

		Button button = new Button(shell, SWT.PUSH);
		button.setText("Dispose");
		button.setBounds(10, 250, 60, 30);
		button.addListener(SWT.Selection, new Listener() {
			public void handleEvent(Event event) {
				root.dispose();
			}
		});
		shell.open();
		while (!shell.isDisposed()) {
			if (!display.readAndDispatch())
				display.sleep();
		}
		display.dispose();
	}
}

Comment 20 Grant Gayed 2003-01-22 11:32:21 EST

Fixed to make this work with gtk 2.0.2.  This should also fix the reported gtk 
2.0.5 case which I can't reproduce.

Comment 21 Christophe Cornu 2003-01-27 14:14:25 EST

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