Community
Participate
Working Groups
Build ID: M20071023-1652 Steps To Reproduce: 1. Launch Eclipse 2. Let Eclipse load (pick workspace if prompted) 3. After Eclipse is fully loaded, or before, mouse over the Eclipse window and it will crash More information: I am using Kubuntu 7.10 with both KDE 3.5.x installed and KDE 4 installed. When running KDE 3.5, Eclipse runs just fine, when running KDE 4, Eclipse crashes immediately upon mousing over the window (that is, I never even get a chance to click on anything). Non of my other application do this, not even NetBeans 6.0 has issues in KDE 4, only Eclipse.
JVM terminated. Exit code=1 /usr/bin/java -Xms80m -Xmx512m -XX:MaxPermSize=512m -jar /opt/eclipse/plugins/org.eclipse.equinox.launcher_1.0.1.R33x_v20070828.jar -os linux -ws gtk -arch x86_64 -showsplash -launcher /opt/eclipse/eclipse -name Eclipse --launcher.library /opt/eclipse/plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.0.2.R331_v20071019/eclipse_1021.so -startup /opt/eclipse/plugins/org.eclipse.equinox.launcher_1.0.1.R33x_v20070828.jar -exitdata 1c25802e -vm /usr/bin/java -vmargs -Xms80m -Xmx512m -XX:MaxPermSize=512m -jar /opt/eclipse/plugins/org.eclipse.equinox.launcher_1.0.1.R33x_v20070828.jar
We need the hs_err_pid*.log or the stack trace of the crash. PW
Created attachment 87298 [details] Crash Log Here is one of my crashes
> # Java VM: IcedTea 64-Bit Server VM (1.7.0-b21 mixed mode linux-amd64) Could you try running Eclipse with a supported JRE? http://www.eclipse.org/eclipse/development/readme_eclipse_3.3.1.1.html#TargetOperatingEnvironments
Sure, I'd love for Eclipse to use my system's default JRE: java version "1.6.0_03" Java(TM) SE Runtime Environment (build 1.6.0_03-b05) Java HotSpot(TM) 64-Bit Server VM (build 1.6.0_03-b05, mixed mode) How can I tell Eclipse to use Sun Java 1.6.0_03 like NetBeans 6.0 does automatically? (In reply to comment #4) > > # Java VM: IcedTea 64-Bit Server VM (1.7.0-b21 mixed mode linux-amd64) > > Could you try running Eclipse with a supported JRE? > http://www.eclipse.org/eclipse/development/readme_eclipse_3.3.1.1.html#TargetOperatingEnvironments >
(In reply to comment #5) > Sure, I'd love for Eclipse to use my system's default JRE: > > java version "1.6.0_03" > Java(TM) SE Runtime Environment (build 1.6.0_03-b05) > Java HotSpot(TM) 64-Bit Server VM (build 1.6.0_03-b05, mixed mode) > > How can I tell Eclipse to use Sun Java 1.6.0_03 like NetBeans 6.0 does > automatically? You could modify your eclipse.ini file or you could just do it from the command line. I am assuming you are using an Eclipse build that was downloaded from eclipse.org. ./eclipse -vm /path/to/sun-java/bin/java Or add... -vm /path/to/sun-java/bin/java ...to your eclipse.ini file. Yes, they need to be on different lines.
I'll try specifying the jre on Monday when I am back in the office and let you know if this fixes the issue. (In reply to comment #6) > (In reply to comment #5) > > Sure, I'd love for Eclipse to use my system's default JRE: > > > > java version "1.6.0_03" > > Java(TM) SE Runtime Environment (build 1.6.0_03-b05) > > Java HotSpot(TM) 64-Bit Server VM (build 1.6.0_03-b05, mixed mode) > > > > How can I tell Eclipse to use Sun Java 1.6.0_03 like NetBeans 6.0 does > > automatically? > > You could modify your eclipse.ini file or you could just do it from the command > line. I am assuming you are using an Eclipse build that was downloaded from > eclipse.org. > > ./eclipse -vm /path/to/sun-java/bin/java > > Or add... > > -vm > /path/to/sun-java/bin/java > > ...to your eclipse.ini file. Yes, they need to be on different lines. >
Error persists: ...$/usr/lib/jvm/java-6-sun/bin/java -version java version "1.6.0_03" Java(TM) SE Runtime Environment (build 1.6.0_03-b05) Java HotSpot(TM) 64-Bit Server VM (build 1.6.0_03-b05, mixed mode) ...$ ./eclipse -vm /usr/lib/jvm/java-6-sun/bin/java JVM terminated. Exit code=1 /usr/lib/jvm/java-6-sun/bin/java -Xms80m -Xmx512m -XX:MaxPermSize=512m -jar /opt/eclipse/plugins/org.eclipse.equinox.launcher_1.0.1.R33x_v20070828.jar -os linux -ws gtk -arch x86_64 -showsplash -launcher /opt/eclipse/eclipse -name Eclipse --launcher.library /opt/eclipse/plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.0.2.R331_v20071019/eclipse_1021.so -startup /opt/eclipse/plugins/org.eclipse.equinox.launcher_1.0.1.R33x_v20070828.jar -exitdata 1c678030 -vm /usr/lib/jvm/java-6-sun/bin/java -vmargs -Xms80m -Xmx512m -XX:MaxPermSize=512m -jar /opt/eclipse/plugins/org.eclipse.equinox.launcher_1.0.1.R33x_v20070828.jar (In reply to comment #7) > I'll try specifying the jre on Monday when I am back in the office and let you > know if this fixes the issue. > > (In reply to comment #6) > > (In reply to comment #5) > > > Sure, I'd love for Eclipse to use my system's default JRE: > > > > > > java version "1.6.0_03" > > > Java(TM) SE Runtime Environment (build 1.6.0_03-b05) > > > Java HotSpot(TM) 64-Bit Server VM (build 1.6.0_03-b05, mixed mode) > > > > > > How can I tell Eclipse to use Sun Java 1.6.0_03 like NetBeans 6.0 does > > > automatically? > > > > You could modify your eclipse.ini file or you could just do it from the command > > line. I am assuming you are using an Eclipse build that was downloaded from > > eclipse.org. > > > > ./eclipse -vm /path/to/sun-java/bin/java > > > > Or add... > > > > -vm > > /path/to/sun-java/bin/java > > > > ...to your eclipse.ini file. Yes, they need to be on different lines. > > >
It looks like you have the correct 64-bit eclipse ... could you please attach the hs_err_<pid>.log from the java6 crash? The java 7 one has a lot of Stub references, but nothing that points into eclipse at all. PW
Sorry, I can't find any hs_err_* newer than 2008-01-14. So, I ran eclipse from the command prompt, here is the output: ...$ /opt/eclipse/eclipse -vm /usr/lib/jvm/java-6-sun/bin/java java.lang.NumberFormatException: For input string: "" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) at java.lang.Long.parseLong(Long.java:424) at java.lang.Long.parseLong(Long.java:461) at java.text.DigitList.getLong(DigitList.java:177) at java.text.DecimalFormat.parse(DecimalFormat.java:1298) at java.text.SimpleDateFormat.subParse(SimpleDateFormat.java:1918) at java.text.SimpleDateFormat.parse(SimpleDateFormat.java:1264) at java.text.DateFormat.parse(DateFormat.java:335) at org.eclipse.mylyn.internal.context.core.SaxContextContentHandler.createEventFromAttributes(SaxContextContentHandler.java:83) at org.eclipse.mylyn.internal.context.core.SaxContextContentHandler.startElement(SaxContextContentHandler.java:62) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:501) at com.sun.org.apache.xerces.internal.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocumentParser.java:179) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:377) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2740) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:645) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:508) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:807) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:107) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205) at org.eclipse.mylyn.internal.context.core.SaxContextReader.readContext(SaxContextReader.java:59) at org.eclipse.mylyn.internal.context.core.InteractionContextExternalizer.readContextFromXML(InteractionContextExternalizer.java:132) at org.eclipse.mylyn.internal.context.core.InteractionContextExternalizer.readContextFromXML(InteractionContextExternalizer.java:121) at org.eclipse.mylyn.internal.context.core.InteractionContextManager.loadActivityMetaContext(InteractionContextManager.java:140) at org.eclipse.mylyn.internal.context.core.InteractionContextManager.getActivityMetaContext(InteractionContextManager.java:132) at org.eclipse.mylyn.internal.context.core.InteractionContextManager.processActivityMetaContextEvent(InteractionContextManager.java:177) at org.eclipse.mylyn.internal.monitor.ui.ShellLifecycleListener.<init>(ShellLifecycleListener.java:35) at org.eclipse.mylyn.monitor.ui.MonitorUiPlugin$2.run(MonitorUiPlugin.java:110) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3296) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2974) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219) at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176) 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.equinox.launcher.Main.invokeFramework(Main.java:508) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447) at org.eclipse.equinox.launcher.Main.run(Main.java:1173) at org.eclipse.equinox.launcher.Main.main(Main.java:1148) (In reply to comment #9) > It looks like you have the correct 64-bit eclipse ... could you please attach > the hs_err_<pid>.log from the java6 crash? The java 7 one has a lot of Stub > references, but nothing that points into eclipse at all. > > PW >
What can happen when this class fails to materialize: org.eclipse.mylyn.internal.monitor.ui.ShellLifecycleListener.<init>(ShellLifecycleListener.java:35) PW
Do you get this error on a non-existent workspace? When prompted, please choose a non-existent folder. Or use -data /path/to/new/folder. Do you get this problem with the Eclipse Classic package?
When prompted, instead of the default workspace, I replaced the string /workspace with /new_workspace and got the same results. About mylyn, is that an addon/feature that I can remove/deactivate? or is it an integral part of eclipse? If I can use eclipse without it, how do I remove/deactivate it? (In reply to comment #12) > Do you get this error on a non-existent workspace? When prompted, please choose > a non-existent folder. > > Or use -data /path/to/new/folder. > > Do you get this problem with the Eclipse Classic package? >
(In reply to comment #13) > When prompted, instead of the default workspace, I replaced the string > /workspace with /new_workspace and got the same results. About mylyn, is that > an addon/feature that I can remove/deactivate? or is it an integral part of > eclipse? If I can use eclipse without it, how do I remove/deactivate it? I don't know how one would deactivate it without going through the Eclipse UI. I suppose you could technically try to remove all traces of org.eclipse.mylyn* in your Eclipse folders. However, I would recommend you just get Eclipse Classic 3.3.1.1 and try to run that instead. This removes a lot of variables since, as you would imagine, deleting things by hand is not the most cleanliest form of plug-in removal.
I created a fresh install and it worked fine in KDE 4. My linux lets me log out of KDE 4 and back into KDE 3.5 so I will now go to KDE 3.5 and remove mylyn and then go back to KDE 4 to see if my full install with all the features I use will work after removing mylyn. (In reply to comment #14) > (In reply to comment #13) > > When prompted, instead of the default workspace, I replaced the string > > /workspace with /new_workspace and got the same results. About mylyn, is that > > an addon/feature that I can remove/deactivate? or is it an integral part of > > eclipse? If I can use eclipse without it, how do I remove/deactivate it? > > I don't know how one would deactivate it without going through the Eclipse UI. > I suppose you could technically try to remove all traces of org.eclipse.mylyn* > in your Eclipse folders. However, I would recommend you just get Eclipse > Classic 3.3.1.1 and try to run that instead. This removes a lot of variables > since, as you would imagine, deleting things by hand is not the most cleanliest > form of plug-in removal. >
I deactivated Mylyn UI and everything that depended on it. When I log into KDE 4 and load my old workspace eclipse still crashes. If however I load new_workspace it runs without crashing. By removing Mylyn UI, what exactly will I not have? Is there anyway to make my workspace work? Or do I just need to make a new one? How come I'm not getting any new hs_err_* files? (In reply to comment #14) > (In reply to comment #13) > > When prompted, instead of the default workspace, I replaced the string > > /workspace with /new_workspace and got the same results. About mylyn, is that > > an addon/feature that I can remove/deactivate? or is it an integral part of > > eclipse? If I can use eclipse without it, how do I remove/deactivate it? > > I don't know how one would deactivate it without going through the Eclipse UI. > I suppose you could technically try to remove all traces of org.eclipse.mylyn* > in your Eclipse folders. However, I would recommend you just get Eclipse > Classic 3.3.1.1 and try to run that instead. This removes a lot of variables > since, as you would imagine, deleting things by hand is not the most cleanliest > form of plug-in removal. >
(In reply to comment #16) > When I log into KDE > 4 and load my old workspace eclipse still crashes. What do the log files say? 'mv .log .log2' and then start Eclipse and see what happens. This way we get fresh log files. > Or do I just need > to make a new one? How come I'm not getting any new hs_err_* files? Those files are created when Sun's JVM has crashed. From your stack traces, that doesn't _appear_ to be the case.
this bug does not appear to be attributed to Mylyn. The stack trace listed in comment#10 was an innocuous problem fixed a while back (bug 210188). If there is any further suspicion you could download the latest (http://www.eclipse.org/mylyn/downloads/ ) and reassugn back to me if there is anything further for us to investigate.
(In reply to comment #16) > I deactivated Mylyn UI and everything that depended on it. When I log into KDE > 4 and load my old workspace eclipse still crashes. If however I load > new_workspace it runs without crashing. By removing Mylyn UI, what exactly > will I not have? Is there anyway to make my workspace work? Or do I just need > to make a new one? How come I'm not getting any new hs_err_* files? If you need to make a new one, you can use File>Import...>Existing projects into workspace to have it correctly copy over the important information about your projects. PW
New Details: It only crashes if I mouse over the Welcome page. On the right I had a Search tab and a Welcome tab. If I carefully followed the top edge of the Eclipse window as I moved the cursor left, once past the Welcome page I could mouse over any other part of the window I wanted without a crash, then as soon as I moused over the Welcome page Eclipse would crash. I have since closed the Welcome tab (mousing over the tab's tab did not crash Eclipse, only mousing over the tab's page). So with the Welcome tab gone from my default workspace, I can now use that workspace in KDE 4. So, that Welcome page, what component does that belong to?
(In reply to comment #20) The Welcome tab is the intro component (part of User Assistance). It is usually your embedded platform browser (if eclipse can find it) or widget that displays content and links. Before you mouse over, do you see a proper eclipse welcome screen (all purple with a number of links) or a scaled down version (possibly just icon links on a white background)? PW
Yes, the Welcome page looks completely normal. Everything loaded, links, icon like graphics, and it crashes when you mouse over any part of it.
Hi Robert, Do you see this crash under any other circumstances? In particlar are you able to open the help system and read documents without any problems? The reason I ask is because Welcome uses an embedded browser as does the help system. Also would you be in a position to test a patch if I created one. If the only thing that doesn't work is the Welcome page then we do have a fallback which is to present a non browser based welcome page, if the problem shows up under other circumstances that would require a different solution.
The description of a crash occurring when mousing over the Welcome page sounds like https://bugs.eclipse.org/bugs/show_bug.cgi?id=209428#c13 . Marking this report a duplicate since I don't think this a UA issue. *** This bug has been marked as a duplicate of bug 209428 ***
I should have mentioned in the last comment, while the other report is being investigated, see if you have environment variable MALLOC_CHECK_ set, and if you do then try running with it unset or set to a value of 0.
