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

Bug 324912

Summary:	Eclipse crashes in latest KDE 4.5.1 when leaving variable proposal table
Product:	z_Archived	Reporter:	Ralph Moenchmeyer <rm>
Component:	PDT	Assignee:	PHP UI <php.ui-inbox>
Status:	CLOSED INVALID	QA Contact:
Severity:	critical
Priority:	P3
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Ralph Moenchmeyer

2010-09-09 18:38:39 EDT

Build Identifier: Build id: 20100617-1415 (Helios Release)

I tried to use Eclipse Helios for PHP development with KDE 4.5.1 (Opensuse 11.3,
x86_64). Today I upgraded to the latest KDE 4.5.1 RPMs of Opensuse's Factory repository.
The rpm for kdebase is kdebase4 4.5.1-178.1-x86_64 from KDE 4 Factory - if that
information helps.

Now there is a new problem with Eclipse and KDE (different from the known
MALLOC-problem in 4.5.0, which has been circumvented recently). Description:

Eclipse starts perfectly. No crash during startup. It loads all the plugins I
use. The PHP editor works normally as long as no dialog window for variable
proposal opens. However, as soon as the dialog with the variable proposal table
is displayed - e.g. when you type $ and wait - you run into trouble when
a) you choose a variable
b) leave the dialog by ESC
c) or klick with the mouse into the editor area again.

Eclipse then crashes immediately.

Messages from the JVM are (Eclipse resides in a directory /samba/eclipse on my
machine):

JVM terminated. Exit code=1
/usr/bin/java
-Dosgi.requiredJavaVersion=1.5
-XX:MaxPermSize=256m
-Xms40m
-Xmx384m
-jar /samba/eclipse//plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar
-os linux
-ws gtk
-arch x86_64
-showsplash
-launcher /samba/eclipse/eclipse
-name Eclipse
--launcher.library
/samba/eclipse//plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.0.v20100503/eclipse_1307.so
-startup
/samba/eclipse//plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar
-exitdata b8006
-product org.eclipse.epp.package.php.product
-vm /usr/bin/java
-vmargs
-Dosgi.requiredJavaVersion=1.5
-XX:MaxPermSize=256m
-Xms40m
-Xmx384m
-jar /samba/eclipse//plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar

Just for testing I tried
MALLOC_CHECK_=0 /samba/eclipse/eclipse

Same problem - same crash.

The same eclipse installation with the same projects, SVN etc. works flawlessly
with a previous 4.5.0 version (with MALLOC_CHECK_=0) and a previous 4.5.1
version.

In addition I tested the same Eclipse implementation for PHP with the very same projects for Opensuse 11.2 and KDE 4.5.0 on the same machine (with MALLOC_CHECK_=0). Then it works perfectly.

Reproducible: Always

Steps to Reproduce:
Open eclipse, open a file in the PHP editor, provoke the opening of a variable
proposal dialog, choose a suggested variable to be used in the editor's code.

Comment 1 Zhongwei Zhao

2010-09-09 22:44:48 EDT

Reproducible: Always ?

Comment 2 Ralph Moenchmeyer

2010-09-10 05:47:54 EDT

(In reply to comment #1)
> Reproducible: Always ?

For the present KDE 4.5.1 package of Opensuse's 11.3 KDE Factory: Yes. 

The crash is independent of the edited file, it is independent of the class, function, position you edit in the file, it is independent of the project and the related SVN repository, it is independent of GTK style (I tried several).
It could not see any difference regarding JRE (SUN, OpenJDK).  

It also occurs when you start eclipse with "-clean". 

The problem may be specific for Opensuse and the present KDE Factory package. I shall test again when new Updates are available. 

Any suggestions what I should try, look at ? 

I can continue my development work with Eclipse as I have another Opensuse installation (11.2, KDE 4.5.0) on my desktop. And here the same Eclipse implementation works.

Comment 3 Ralph Moenchmeyer

2010-09-10 16:02:40 EDT

Meanwhile I did a clean reinstall of Opensuse 11.3 from scratch, updated to KDE 4.5.1 and updated glibc. 

I reinstalled Eclipse and tested for a fresh project.  

No problems any longer. 

So my problem resulted from other package updates and not from KDE 4.5.1. 

I shall try to narrow down the problem but for the time being I think I close the bug as the connection of my problem to KDE 4.5.1 could be be misleading.