Trolltech Home | Qt-jambi-interest Home | Recent Threads | All Threads | Author | Date
All threads index page 1

Qt-jambi-interest Archive, May 2007
eclipse crashing when opening ui file


Message 1 in thread

Hello,

I installed qtjambi beta 2 on my Fedora Core 6 computer with Fedora Eclipse
3.2.2. All looks fine until I try to open ui file. Then Eclipse crashes. I
searched for possible resolutions and found messages about the conflicting
qt library versions when using Qt themes in Gtk, but I do not know if it is
the case. My KDE is on Keramik and Gnome is on Clearlooks.
Gnome-control-center theme changes are immediatelly seen on Eclipse.

The crash produces following information.


When opening ui file Eclipse crashed and displayed dialog with:

JVM is

[root@hal9000 ld.so.conf.d]# java -version
java version "1.6.0_01"
Java(TM) SE Runtime Environment (build 1.6.0_01-b06)
Java HotSpot(TM) Server VM (build 1.6.0_01-b06, mixed mode)


JVM terminated. Exit code=1
/usr/java/jdk/bin/java
-Xms40m
-Xmx256m
-Dosgi.sharedConfiguration.area=/usr/lib/eclipse/configuration
-jar /usr/share/eclipse/startup.jar
-os linux
-ws gtk
-arch x86
-launcher /usr/bin/eclipse
-name Eclipse
-showsplash 600
-exitdata 850025
-vm /usr/java/jdk/bin/java
-vmargs
-Xms40m
-Xmx256m
-Dosgi.sharedConfiguration.area=/usr/lib/eclipse/configuration
-jar /usr/share/eclipse/startup.jar


Console showed this:

[ph@hal9000 mysql]$ eclipse
Error occurred during initialization of VM
java.lang.ArrayStoreException: java.security.ProtectionDomain
        at com.trolltech.qtdesigner.views.FormWindowW.initializeJambiPlugins(Native
Method)
        at com.trolltech.qtdesigner.views.FormWindowW.initializeJambiPlugins
(FormWindowW.java:141)
        at com.trolltech.qtdesigner.qtjambi.QtJambiConnection.loadPlugins(
QtJambiConnection.java:201)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(
NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at com.trolltech.qtdesigner.views.FormWindowW.<init>(
FormWindowW.java:50)
        at com.trolltech.qtdesigner.qtjambi.JambiUiEditor.createPartControl(
JambiUiEditor.java:21)
        at org.eclipse.ui.internal.EditorReference.createPartHelper(
EditorReference.java:596)
        at org.eclipse.ui.internal.EditorReference.createPart(
EditorReference.java:372)
        at org.eclipse.ui.internal.WorkbenchPartReference.getPart(
WorkbenchPartReference.java:566)
        at org.eclipse.ui.internal.EditorReference.getEditor(
EditorReference.java:214)
        at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(
WorkbenchPage.java:2595)
        at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(
WorkbenchPage.java:2528)
        at org.eclipse.ui.internal.WorkbenchPage.access$10(
WorkbenchPage.java:2520)
        at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.java
:2505)
        at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java
:67)
        at org.eclipse.ui.internal.WorkbenchPage.openEditor(
WorkbenchPage.java:2500)
        at org.eclipse.ui.internal.WorkbenchPage.openEditor(
WorkbenchPage.java:2485)
        at org.eclipse.ui.ide.IDE.openEditor(IDE.java:388)
        at org.eclipse.ui.ide.IDE.openEditor(IDE.java:350)
        at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor
(EditorUtility.java:275)
        at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor
(EditorUtility.java:139)
        at org.eclipse.jdt.internal.ui.actions.OpenActionUtil.open(
OpenActionUtil.java:49)
        at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:190)
        at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:174)
        at org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(
SelectionDispatchAction.java:267)
        at org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(
SelectionDispatchAction.java:243)
        at
org.eclipse.jdt.internal.ui.packageview.PackageExplorerActionGroup.handleOpen
(PackageExplorerActionGroup.java:306)
        at
org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart$4.open(
PackageExplorerPart.java:653)
        at org.eclipse.jface.viewers.StructuredViewer$2.run(
StructuredViewer.java:817)
        at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
        at org.eclipse.core.runtime.Platform.run(Platform.java:848)
        at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:44)
        at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:149)
        at org.eclipse.jface.viewers.StructuredViewer.fireOpen(
StructuredViewer.java:815)
        at org.eclipse.jface.viewers.StructuredViewer.handleOpen(
StructuredViewer.java:1069)
        at org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(
StructuredViewer.java:1168)
        at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(
OpenStrategy.java:249)
        at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java
:243)
        at org.eclipse.jface.util.OpenStrategy$1.mouseSelectItem(
OpenStrategy.java:414)
        at org.eclipse.jface.util.OpenStrategy$1.handleEvent(
OpenStrategy.java:350)
        at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
        at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1085)
        at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java
:3180)
        at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java
:2856)
        at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java
:1930)
        at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1894)
        at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(
Workbench.java:422)
        at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java
:149)
        at org.eclipse.ui.internal.ide.IDEApplication.run(
IDEApplication.java:95)
        at org.eclipse.core.internal.runtime.PlatformActivator$1.run(
PlatformActivator.java:78)
        at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(
EclipseAppLauncher.java:92)
        at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(
EclipseAppLauncher.java:68)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(
EclipseStarter.java:400)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(
EclipseStarter.java:177)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(
NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
        at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
        at org.eclipse.core.launcher.Main.run(Main.java:977)
        at org.eclipse.core.launcher.Main.main(Main.java:952)

Some information about my computer and qt libs:

[ph@hal9000 mysql]$ ll /etc/ld.so.conf.d/
total 28
-rw-r--r-- 1 root root 15 Apr  7  2006 ingres.conf
-rw-r--r-- 1 root root 15 Jul 12  2006 mysqlclient10-i386.conf
-rw-r--r-- 1 root root 15 Nov 23 06:42 mysql-i386.conf
-rw-r--r-- 1 root root 17 Apr 20  2006 panda3d.conf
-rw-r--r-- 1 root root 20 Oct 23  2006 qt-i386.conf
-rw-r--r-- 1 root root 17 May  8 09:45 qtjambi.conf
-rw-r--r-- 1 root root 15 Jan  2  2006 wine-32.conf

Here I removed qtjambi and put the lib path to qt-i386 as first entry and
ran ldconfig

[ph@hal9000 mysql]$ cat /etc/ld.so.conf.d/qt
qt-i386.conf  qtjambi.conf
[ph@hal9000 mysql]$ cat /etc/ld.so.conf.d/qt*
/usr/lib/qt-3.3/lib
/opt/qtjambi/lib
[ph@hal9000 mysql]$

[ph@hal9000 mysql]$ which eclipse
/usr/bin/eclipse
[ph@hal9000 mysql]$ ldd /usr/bin/eclipse
        linux-gate.so.1 =>  (0x00658000)
        libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0 (0x04d5f000)
        libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0(0x005d5000)
        libgobject-2.0.so.0 => /lib/libgobject-2.0.so.0 (0x07a21000)
        libgdk-x11-2.0.so.0 => /usr/lib/libgdk-x11-2.0.so.0 (0x00ac8000)
        libc.so.6 => /lib/libc.so.6 (0x00bf2000)
        libglib-2.0.so.0 => /lib/libglib-2.0.so.0 (0x02abc000)
        libpangocairo-1.0.so.0 => /usr/lib/libpangocairo-1.0.so.0(0x005ca000)
        libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0x00a87000)
        libX11.so.6 => /usr/lib/libX11.so.6 (0x00101000)
        libXfixes.so.3 => /usr/lib/libXfixes.so.3 (0x00de2000)
        libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0 (0x07abc000)
        libgmodule-2.0.so.0 => /lib/libgmodule-2.0.so.0 (0x0021d000)
        libdl.so.2 => /lib/libdl.so.2 (0x00d5a000)
        libcairo.so.2 => /usr/lib/libcairo.so.2 (0x04cf1000)
        libm.so.6 => /lib/libm.so.6 (0x00d31000)
        libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x05388000)
        libXext.so.6 => /usr/lib/libXext.so.6 (0x00d9b000)
        libXrender.so.1 => /usr/lib/libXrender.so.1 (0x00dec000)
        libXinerama.so.1 => /usr/lib/libXinerama.so.1 (0x00bcd000)
        libXi.so.6 => /usr/lib/libXi.so.6 (0x00205000)
        libXrandr.so.2 => /usr/lib/libXrandr.so.2 (0x00df7000)
        libXcursor.so.1 => /usr/lib/libXcursor.so.1 (0x04ce5000)
        /lib/ld-linux.so.2 (0x00bd5000)
        libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0 (0x0059a000)
        libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x052bb000)
        libXau.so.6 => /usr/lib/libXau.so.6 (0x00d8e000)
        libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0x00d93000)
        libz.so.1 => /usr/lib/libz.so.1 (0x00d79000)
        libpng12.so.0 => /usr/lib/libpng12.so.0 (0x0533d000)
        libexpat.so.0 => /lib/libexpat.so.0 (0x05365000)
[ph@hal9000 mysql]$

Best regards,

Petr

Message 2 in thread

On Wednesday 09 May 2007 20:55, Petr Hrasky wrote:
> Hello,
>
> I installed qtjambi beta 2 on my Fedora Core 6 computer with Fedora Eclipse
> 3.2.2. All looks fine until I try to open ui file. Then Eclipse crashes. I
> searched for possible resolutions and found messages about the conflicting
> qt library versions when using Qt themes in Gtk, but I do not know if it is
> the case. My KDE is on Keramik and Gnome is on Clearlooks.
> Gnome-control-center theme changes are immediatelly seen on Eclipse.
>
> The crash produces following information.
>
>
> When opening ui file Eclipse crashed and displayed dialog with:
>
> JVM is
>
> [root@hal9000 ld.so.conf.d]# java -version
> java version "1.6.0_01"
> Java(TM) SE Runtime Environment (build 1.6.0_01-b06)
> Java HotSpot(TM) Server VM (build 1.6.0_01-b06, mixed mode)

Hi, we are currently only supporting the client version of the JVM. This will 
be fixed for the next release. Sorry for the inconvenience.

Let us know if the problem persists, if you try the client version.

Best regards 
	HÃvard F


Message 3 in thread

Hi Håvard,

you got it! I changed eclipse.ini to include -client switch and it starts up
Designer. In the process I learned that my computer is server class by the
Java VM. Now onto some testing.

Thanks and

Best regards,


On 5/10/07, Håvard Frøiland <hfroilan@xxxxxxxxxxxxx> wrote:
>
> On Wednesday 09 May 2007 20:55, Petr Hrasky wrote:
> > Hello,
> >
> > I installed qtjambi beta 2 on my Fedora Core 6 computer with Fedora
> Eclipse
> > 3.2.2. All looks fine until I try to open ui file. Then Eclipse crashes.
> I
> > searched for possible resolutions and found messages about the
> conflicting
> > qt library versions when using Qt themes in Gtk, but I do not know if it
> is
> > the case. My KDE is on Keramik and Gnome is on Clearlooks.
> > Gnome-control-center theme changes are immediatelly seen on Eclipse.
> >
> > The crash produces following information.
> >
> >
> > When opening ui file Eclipse crashed and displayed dialog with:
> >
> > JVM is
> >
> > [root@hal9000 ld.so.conf.d]# java -version
> > java version "1.6.0_01"
> > Java(TM) SE Runtime Environment (build 1.6.0_01-b06)
> > Java HotSpot(TM) Server VM (build 1.6.0_01-b06, mixed mode)
>
> Hi, we are currently only supporting the client version of the JVM. This
> will
> be fixed for the next release. Sorry for the inconvenience.
>
> Let us know if the problem persists, if you try the client version.
>
> Best regards
>         Håvard F
>
>

Message 4 in thread

Håvard,

One more thing. Eclipse crashed on exit. I think I saw something similar on
the list.

Following messages from crash:

ph@hal9000 mysql]$ eclipse
QPixmap::scaled: Pixmap is a null pixmap
QObjects can only be implicitly garbage collected when owned by a QThread,
native resource ('' [QObject]) is leaked
#
# An unexpected error has been detected by Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0xb235653c, pid=6964, tid=3049745296
#
# Java VM: Java HotSpot(TM) Client VM (1.6.0_01-b06 mixed mode, sharing)
# Problematic frame:
# C  [libqtjambi.so+0x1753c]  _Z18qtjambi_find_classP7JNIEnv_PKc+0x2c
#
# An error report file with more information is saved as hs_err_pid6964.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
#


JVM terminated. Exit code=1
/usr/java/jdk/bin/java
-client
-Xms40m
-Xmx256m
-Dosgi.sharedConfiguration.area=/usr/lib/eclipse/configuration
-jar /usr/share/eclipse/startup.jar
-os linux
-ws gtk
-arch x86
-launcher /usr/bin/eclipse
-name Eclipse
-showsplash 600
-exitdata 1e0014
-vm /usr/java/jdk/bin/java
-vmargs
-client
-Xms40m
-Xmx256m
-Dosgi.sharedConfiguration.area=/usr/lib/eclipse/configuration
-jar /usr/share/eclipse/startup.jar

On 5/10/07, Petr Hrasky <phrasky@xxxxxxxxx> wrote:
>
> Hi Håvard,
>
> you got it! I changed eclipse.ini to include -client switch and it starts
> up Designer. In the process I learned that my computer is server class by
> the Java VM. Now onto some testing.
>
> Thanks and
>
> Best regards,
>
>
> On 5/10/07, Håvard Frøiland <hfroilan@xxxxxxxxxxxxx> wrote:
> >
> > On Wednesday 09 May 2007 20:55, Petr Hrasky wrote:
> > > Hello,
> > >
> > > I installed qtjambi beta 2 on my Fedora Core 6 computer with Fedora
> > Eclipse
> > > 3.2.2. All looks fine until I try to open ui file. Then Eclipse
> > crashes. I
> > > searched for possible resolutions and found messages about the
> > conflicting
> > > qt library versions when using Qt themes in Gtk, but I do not know if
> > it is
> > > the case. My KDE is on Keramik and Gnome is on Clearlooks.
> > > Gnome-control-center theme changes are immediatelly seen on Eclipse.
> > >
> > > The crash produces following information.
> > >
> > >
> > > When opening ui file Eclipse crashed and displayed dialog with:
> > >
> > > JVM is
> > >
> > > [root@hal9000 ld.so.conf.d]# java -version
> > > java version "1.6.0_01"
> > > Java(TM) SE Runtime Environment (build 1.6.0_01-b06)
> > > Java HotSpot(TM) Server VM (build 1.6.0_01-b06, mixed mode)
> >
> > Hi, we are currently only supporting the client version of the JVM. This
> > will
> > be fixed for the next release. Sorry for the inconvenience.
> >
> > Let us know if the problem persists, if you try the client version.
> >
> > Best regards
> >         Håvard F
> >
> >
>

Message 5 in thread

On Thursday 10 May 2007 19:37, Petr Hrasky wrote:
> HÃvard,
>
> One more thing. Eclipse crashed on exit. I think I saw something similar on
> the list.
>

Hi, the crash on exit is harmless, but still annoying. We will try to find a 
solution for this in one of the upcoming releases.

Thanks for reporting problems that you find. 

Best regards
	HÃvard F

> Following messages from crash:
>
> ph@hal9000 mysql]$ eclipse
> QPixmap::scaled: Pixmap is a null pixmap
> QObjects can only be implicitly garbage collected when owned by a QThread,
> native resource ('' [QObject]) is leaked
> #
> # An unexpected error has been detected by Java Runtime Environment:
> #
> #  SIGSEGV (0xb) at pc=0xb235653c, pid=6964, tid=3049745296
> #
> # Java VM: Java HotSpot(TM) Client VM (1.6.0_01-b06 mixed mode, sharing)
> # Problematic frame:
> # C  [libqtjambi.so+0x1753c]  _Z18qtjambi_find_classP7JNIEnv_PKc+0x2c
> #
> # An error report file with more information is saved as hs_err_pid6964.log
> #
> # If you would like to submit a bug report, please visit:
> #   http://java.sun.com/webapps/bugreport/crash.jsp
> #
>
>
> JVM terminated. Exit code=1
> /usr/java/jdk/bin/java
> -client
> -Xms40m
> -Xmx256m
> -Dosgi.sharedConfiguration.area=/usr/lib/eclipse/configuration
> -jar /usr/share/eclipse/startup.jar
> -os linux
> -ws gtk
> -arch x86
> -launcher /usr/bin/eclipse
> -name Eclipse
> -showsplash 600
> -exitdata 1e0014
> -vm /usr/java/jdk/bin/java
> -vmargs
> -client
> -Xms40m
> -Xmx256m
> -Dosgi.sharedConfiguration.area=/usr/lib/eclipse/configuration
> -jar /usr/share/eclipse/startup.jar
>
> On 5/10/07, Petr Hrasky <phrasky@xxxxxxxxx> wrote:
> > Hi HÃvard,
> >
> > you got it! I changed eclipse.ini to include -client switch and it starts
> > up Designer. In the process I learned that my computer is server class by
> > the Java VM. Now onto some testing.
> >
> > Thanks and
> >
> > Best regards,
> >
> > On 5/10/07, HÃvard FrÃiland <hfroilan@xxxxxxxxxxxxx> wrote:
> > > On Wednesday 09 May 2007 20:55, Petr Hrasky wrote:
> > > > Hello,
> > > >
> > > > I installed qtjambi beta 2 on my Fedora Core 6 computer with Fedora
> > >
> > > Eclipse
> > >
> > > > 3.2.2. All looks fine until I try to open ui file. Then Eclipse
> > >
> > > crashes. I
> > >
> > > > searched for possible resolutions and found messages about the
> > >
> > > conflicting
> > >
> > > > qt library versions when using Qt themes in Gtk, but I do not know if
> > >
> > > it is
> > >
> > > > the case. My KDE is on Keramik and Gnome is on Clearlooks.
> > > > Gnome-control-center theme changes are immediatelly seen on Eclipse.
> > > >
> > > > The crash produces following information.
> > > >
> > > >
> > > > When opening ui file Eclipse crashed and displayed dialog with:
> > > >
> > > > JVM is
> > > >
> > > > [root@hal9000 ld.so.conf.d]# java -version
> > > > java version "1.6.0_01"
> > > > Java(TM) SE Runtime Environment (build 1.6.0_01-b06)
> > > > Java HotSpot(TM) Server VM (build 1.6.0_01-b06, mixed mode)
> > >
> > > Hi, we are currently only supporting the client version of the JVM.
> > > This will
> > > be fixed for the next release. Sorry for the inconvenience.
> > >
> > > Let us know if the problem persists, if you try the client version.
> > >
> > > Best regards
> > >         HÃvard F