[Randy]

Hi,
I get a repeatable crash on linux when I start eclipse to use the new editor with the following code:

#!/bin/bash
export MOZILLA_FIVE_HOME=""
/usr/local/randy/bin/eclipse-3.2/eclipse -vmargs -Xms128M -Xmx512M -XX:PermSize=64M -XX:MaxPermSize=128M

It runs ok if I start eclipse without the MOZILLA_FIVE_HOME option, but I get the Save Failed: Null dialog when I save a JSP.

I’ve several core dumps from the java runtime that are quite large, so rather pasting them, I’d rather attach them (not sure how to do this) or email them. Also, I have my eclipse logs and there are exceptions in them. Again, I’d like to attach them or email them. Feel free to contact me with my email that is on file

I had this problem on an update, so I whacked everything and did a clean install. The only thing common is the workspace. I can use this workspace on another machine and the new java editor (on a laptop, configured with gentoo very much like my work machine) and it seems to work. I did start eclipse with the -clean option

My config:
– System Setup ——————————-
Operating System and version: Gentoo Linux
Eclipse version: 3.2
Eclipse build id: M20060629-1905
Fresh Eclipse install (y/n): y
If not, was it upgraded to its current version using the update manager?
Other installed external plugins: PMD 3.7, subclipse 1.2
Number of plugins in the <eclipse>/plugins directory that begin with org.eclipse.pde.*:
MyEclipse version: M20060629-1905
Eclipse JDK version: 1.5.08
Application Server JDK version: 1.5.08
Are there any exceptions in the Eclipse log file? yes. I’d like to email them or attach them as there is a LOT of data.

If this is a DB related question please answer the following:

RDBMS vendor and version:
JDBC driver vendor and version, and access type (thin, type-2, etc):
Connection URL:
Eclipse error logs related to com.genuitec.eclipse.sqlexplorer packages:

– Message Body ——————————-

[Riyad Kalla]

Before you do that, please upgrade to the build 98 or later of JDK 6 from https://mustang.dev.java.net and try and run MyEclipse with that. I have a local install of Ubuntu and specifically with JDK 1.5.0_08 MyEclipse crashes left and right, it almost always seems related to the permgen space, but as soon as I moved over to JDK 6, the crashes stopped, so it seemed to be something with that particular version of the VM on Linux. You can also try downgrading to 1.4.2_12.

More detail here: http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-14136.html

[arjan.tijms]

@support-rkalla wrote:

Before you do that, please upgrade to the build 98 or later of JDK 6 from https://mustang.dev.java.net and try and run MyEclipse with that. I have a local install of Ubuntu and specifically with JDK 1.5.0_08 MyEclipse crashes left and right, it almost always seems related to the permgen space,

That’s strange. I’m running on Debian testing with a 2.6.15 kernel and I’m using JDK 1.5.0_08. I haven’t seen any frequent crashes with Eclipse, while my system should be quite close to the one you’re describing. YFYI, before 1.5.0_08 I used Java 6 beta 2, but on your specific request I downgraded to this version because of the earlier “save failed: null” problems. (Downgrading didn’t helped btw, but I just decided to stay on 1.5.0_08 for a while before switching back).

[Riyad Kalla]

Arjan,
That is very odd, I had another gentleman on support@ that was on Ubuntu having the same problem I was (with the crashing with 1.5.0) but if you are on Debian with the same kernel and not crashing out left and right… makes me thing there is something squirrely with some libs on Dapper Drake.

Do you have any other linux boxes handy to run MyEclipse on, maybe one with Gentoo/SUSE/etc. on them?

[arjan.tijms]

I’m afraid we don’t have any other Linux boxes than Debian ones available. There’s a PPC machine running Ubuntu here though, but there’s no SUN JVM for Linux/PPC as far as I know.

Most people in our team are still running Eclipse 3.1/MyEclipse 4 though because of the problems with the new MyEclipse version. One other person is (mainly) on Eclipse 3.2/MyEclipse 5/Debian testing/SUN 5 JDK and I haven’t heard anything about frequent crashes. I asked one other person who’s using Ubuntu 6.06 and Eclipse 3.2, but he’s using SUN JDK 6 so also doesn’t see any crashes.

Hope this helps.

[Randy]

I’m running gentoo on 2 different boxes, one a laptop. Kernel rev is 2.6.17-gentoo-r7. The laptop was recently recompiled to use gcc 4.1. My work box is still compiled with 3.4.something. Glibc 2.4-r3 on my laptop (I’m out from work this week so I can’t check what it is running). Is there any other information/testing that I can do? I’m glad to help.

I haven’t had a chance to try the 1.6 jdk. I’m assuming that I can still have all of my code, and host tomcat from the 1.5 jdk, as I can’t switch jdk’s for the project?

Randy

addendum. If I run myeclipse with the MOZILLA_FIVE_HOME=”” I get the jre crashes/stacktraces. If I run withouth using the above env, I get the save failed null errors, and a lot of jsp files with an extension of jsp_wd3_init.html. These are . files (ie hidden) and contain the following:

randy@dragon ~/workspace/AssetmgmtPersistence $ more webclient/pages/protected/pcmgmt/edit/.promote_new_prodcat.jsp_wd3_init.html
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><h
tml><head></head><body><body></html>

[Riyad Kalla]

Randy,

I haven’t had a chance to try the 1.6 jdk. I’m assuming that I can still have all of my code, and host tomcat from the 1.5 jdk, as I can’t switch jdk’s for the project?

Yes that’s correct.

addendum. If I run myeclipse with the MOZILLA_FIVE_HOME=”” I get the jre crashes/stacktraces. If I run withouth using the above env, I get the save failed null errors, and a lot of jsp files with an extension of jsp_wd3_init.html. These are . files (ie hidden) and contain the following:

This sounds similar to what I saw except as soon as I switched JDKs from 1.5.0, the constant crashes stopped. I’m trying to figure out if this is a VM bug of MyEclipse bug. I’ve talked with management and this is a high priority so the more info we gather the better.

[Riyad Kalla]

Arjan,
Could you be more specific about some of the problems that cause your team to stay with Eclipse 3.1/MyEclipse 4.1?

[arjan.tijms]

A lot of problems have already been reported in other threads. It are mainly validation issues, so many things are flagged as errors or warnings now in the majority of our source files. I don’t want to expose our less experienced programmers to that yet.

Another problem is that when you save a jsp or html file, the editor comes with a dialog saying saving has failed. On Linux there’s the MOZILLA_FIVE_HOME workaround for this, but I still haven’t seen anything for Windows. (there’s one person who’s using Windows here, and we want to switch for all developpers at the same time)

[Riyad Kalla]

I’m digging up and cross-linking all the reports we have on Linux right now to try and come up with a concise report for the developers. It turns out that a common theme in almost all the PIDs we have collected to look at is a crash with an interaction between Java and some native libs MyEclipse uses for the designer so there *is* definately a starting point for us to look into with regard to the designer crashing.

Right now I’m trying to dig up more info on other setups and causes of other crashes. For example, when I was testing, opening up the UML designer and Matisse4MyEclipse then doing something like adding JSF capabilities or Spring capabilities to a project would cause it to crash. Can you guys try that locally for me?

[Randy]

Hi,
I’ve more to add to this. I’m currently in the middle of a deadline, so I haven’t had a chance to try your suggestions yet, but will hopefully have some time this weekend.

The observations I had last night were new. I bring work home by checking out my project onto a usb thumbdrive, and copying it into my local workspace on my laptop at home. This has worked great for a year. Last night, when I started eclipse after copying, I kept getting lockups during the rebuild workspace message. The lockup for the most part froze X windows. My mouse was repsonsive, but I could not get focus to change to any other window. I ended up killing X (ctrl-alt-backspace). This was repeatable. I was starting eclipse with the old editor (ie not using the mozilla path trick). The only other thing that was a bit different was that I must have closed my last session while in the debug editor, since the window that opened up was the debugger view. The menus would be responsive for a bit, until about the Rebuilding Workspace message was at about 3 percent. Then it broke. There was no jvm log that I could find, and the only messages in the WORKSPACE/.metadata/.log file was about resource is out of sync with filesystem. I did try starting eclipse with the -clean option for grins, but same problem.

End result was that I downloaded the manual install option of myeclipse, then removed (ok, moved) eclipse 3.2 and myeclipse 5.0.1 and reinstalled. Everything seems to be ok now.

my laptop is the same as my work box, gentoo, with the latest stable updates.

If I find out more, I’ll post again.

Tx!

[Riyad Kalla]

Wow that’s a bit extreme, I don’t know if MyEclipse/Eclipse can lockup X on it’s own but if you were able to reproduce this each time that doesn’t sound good.

I’m hoping when we get a chance to dig down into this we will able to put into place multiple layers of redundancy and error catching-checking which will stop things from dying and instead be more graceful/informative.

From the few short moments I’ve talked to the dev guys about this, it sounds like it’s dooable.

[Randy]

Hi,
I’ve got more information on this, as I have struggled with this problem on my workbox all day today. Wierd thing is that this is something somewhat new. The symptom is that the load overage on my box shoots throgh the roof, well over 20. Here is what is in my .metalog/.log. I previosly backed up the older .log and deleted it, so this is everything that happened just for this one lockup. I ended up killing X then restarting X. I have not started up eclipse again.

I started eclipse without the mozilla env var, so I was using the original JSP editor. The only thing open were some JSPs (using JSF).

One other thing of note, is that the JSP and the JSF validtor have recently been using a LOT of cpu. not sure why. I installed myeclipse using the installer, but I think I will use the manual install next time (I might end up cleaning it up and starting over).

The only plugins I have are PMD, and subclipse.

randy@aeglinux02 ~/workspace/.metadata $ more .log
!SESSION 2006-09-22 11:17:14.757 ———————————————–
eclipse.buildId=M20060629-1905
java.version=1.5.0_08
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Command-line arguments: -os linux -ws gtk -arch x86

!ENTRY org.eclipse.core.resources 2 10035 2006-09-22 11:17:30.487
!MESSAGE A workspace crash was detected. The previous session did not exit normally.

!ENTRY org.eclipse.wst.internet.cache 1 0 2006-09-22 11:17:51.645
!MESSAGE wtp.autotest.noninteractive is set. Licenses dialogs will not be displayed.

!ENTRY org.eclipse.update.core 4 0 2006-09-22 11:18:46.076
!MESSAGE Digest could not be parsed:Unable to retrieve remote reference “http://download.eclipse.org/updates/3.2/
digest.zip”. [Server returned HTTP response code: “404 Not Found” for URL: http://download.eclipse.org/updates/3.
2/digest.zip.]

!ENTRY net.sourceforge.pmd.runtime 1 0 2006-09-22 11:18:53.580
!MESSAGE 0 markers applied on 0 files in 0ms.

!ENTRY net.sourceforge.pmd.runtime 1 0 2006-09-22 11:18:53.759
!MESSAGE Review code command terminated. 298 rules were executed against 0 files. PMD was not executed.

!ENTRY net.sourceforge.pmd.runtime 1 0 2006-09-22 11:18:53.760
!MESSAGE Command ReviewCode excecuted in 4031ms

!ENTRY net.sourceforge.pmd.runtime 1 0 2006-09-22 11:18:54.964
!MESSAGE 0 markers applied on 0 files in 0ms.

!ENTRY net.sourceforge.pmd.runtime 1 0 2006-09-22 11:18:54.973
!MESSAGE Review code command terminated. 303 rules were executed against 0 files. PMD was not executed.

!ENTRY net.sourceforge.pmd.runtime 1 0 2006-09-22 11:18:54.974
!MESSAGE Command ReviewCode excecuted in 841ms

!ENTRY org.eclipse.osgi 2 1 2006-09-22 11:19:12.251
!MESSAGE NLS unused message: QF_NEW_BEAN_PROPOSAL in: org.eclipse.jst.jsf.validation.internal.el.diagnostics.mess
ages

!ENTRY org.eclipse.ui 4 4 2006-09-22 11:38:11.101
!MESSAGE Unhandled event loop exception

!ENTRY org.eclipse.ui 4 0 2006-09-22 11:38:11.156
!MESSAGE Widget is disposed
!STACK 0
org.eclipse.swt.SWTException: Widget is disposed
at org.eclipse.swt.SWT.error(SWT.java:3374)
at org.eclipse.swt.SWT.error(SWT.java:3297)
at org.eclipse.swt.SWT.error(SWT.java:3268)
at org.eclipse.swt.widgets.Widget.error(Widget.java:434)
at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:372)
at org.eclipse.swt.widgets.Table.getItems(Table.java:1432)
at org.eclipse.jface.viewers.CheckboxTableViewer.preservingSelection(CheckboxTableViewer.java:278)
at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1413)
at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1370)
at com.genuitec.eclipse.ast.deploy.core.ui.dialog.DeploymentManagerDialog$8.run(Unknown Source)
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:3141)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2843)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419)
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:585)
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)

[Randy]

Also, in the previous log file there are a lot of null pointer exceptions (I think these may actually be associated to the save jsp error dialog, but I’m not sure).:

!ENTRY org.eclipse.ui 2 0 2006-09-19 13:49:43.159
!MESSAGE Save Failed
!STACK 0
java.lang.NullPointerException
at com.genuitec.eclipse.webdesigner3.design.DesignEditSystem.setEditorDocumentRoot(DesignEditSystem.java:
114)
at com.genuitec.eclipse.webdesigner3.design.DesignEditSystem.synchronize(DesignEditSystem.java:165)
at com.genuitec.eclipse.webdesigner3.AbstractEditSystem.setSynchronized(AbstractEditSystem.java:24)
at com.genuitec.eclipse.webdesigner3.WebDesigner3.setSynchronized(WebDesigner3.java:83)
at com.genuitec.eclipse.webdesigner3.editors.WebDesignerMultiPageEditor.checkSynchronization(WebDesignerM
ultiPageEditor.java:577)
at com.genuitec.eclipse.webdesigner3.editors.WebDesignerMultiPageEditor.doSave(WebDesignerMultiPageEditor
.java:464)
at org.eclipse.ui.internal.SaveableHelper$1.run(SaveableHelper.java:131)
at org.eclipse.ui.internal.SaveableHelper$4.run(SaveableHelper.java:252)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:369)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:313)
at org.eclipse.jface.window.ApplicationWindow$1.run(ApplicationWindow.java:763)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
at org.eclipse.jface.window.ApplicationWindow.run(ApplicationWindow.java:760)
at org.eclipse.ui.internal.WorkbenchWindow.run(WorkbenchWindow.java:2283)
at org.eclipse.ui.internal.SaveableHelper.runProgressMonitorOperation(SaveableHelper.java:258)
at org.eclipse.ui.internal.SaveableHelper.savePart(SaveableHelper.java:136)
at org.eclipse.ui.internal.EditorManager.savePart(EditorManager.java:1360)
at org.eclipse.ui.internal.WorkbenchPage.savePart(WorkbenchPage.java:2978)
at org.eclipse.ui.internal.WorkbenchPage.saveEditor(WorkbenchPage.java:2991)
at org.eclipse.ui.internal.SaveAction.run(SaveAction.java:67)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:499)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:539)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488)
at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:441)
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:3164)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2840)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419)
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:585)
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)

[Riyad Kalla]

I’m filing all this information into the respective bugs to be looked into, thank you for taking the time to work with us on this issue.

[Author]

Posts