Does the process leave some log file behind? Usually, it's creating either a core dump file (which is really hard to diagnose) or a file call hs_err_pidxyz.log. Do you find any of these in your home/working directories?
Is there anything abnormal in .metadata/.log file or any hs_err_pidxyzlog files in the KNIME installation directory? Thanks for looking into it, again.
I've upgraded my OS to 10.4 and knime to the latest version, but it keeps on crashing.
This is the last part of the .metadata/.log file
!ENTRY org.eclipse.ui.intro 4 0 2011-10-06 16:38:28.946
!MESSAGE Could not run action: org.knime.workbench.help.intro.NewProjectWizardIntroAction
!STACK 0
java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
at org.knime.workbench.help.intro.NewProjectWizardIntroAction.run(NewProjectWizardIntroAction.java:110)
at org.eclipse.ui.internal.intro.impl.model.url.IntroURL.runAction(IntroURL.java:282)
at org.eclipse.ui.internal.intro.impl.model.url.IntroURL.doExecute(IntroURL.java:193)
at org.eclipse.ui.internal.intro.impl.model.url.IntroURL$1.run(IntroURL.java:144)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.ui.internal.intro.impl.model.url.IntroURL.execute(IntroURL.java:141)
at org.eclipse.ui.internal.intro.impl.model.url.IntroURL.handleCustomAction(IntroURL.java:623)
at org.eclipse.ui.internal.intro.impl.model.url.IntroURL.doExecute(IntroURL.java:214)
at org.eclipse.ui.internal.intro.impl.model.url.IntroURL$1.run(IntroURL.java:144)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.ui.internal.intro.impl.model.url.IntroURL.execute(IntroURL.java:141)
at org.eclipse.ui.internal.intro.impl.presentations.BrowserIntroPartLocationListener.changing(BrowserIntroPartLocationListener.java:130)
at org.eclipse.swt.browser.Mozilla.OnStartURIOpen(Mozilla.java:3891)
at org.eclipse.swt.browser.Mozilla$17.method3(Mozilla.java:1056)
at org.eclipse.swt.internal.mozilla.XPCOMObject.callback3(XPCOMObject.java:266)
at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method)
at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2229)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3159)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.knime.product.rcp.KNIMEApplication.start(KNIMEApplication.java:95)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
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:619)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
at org.eclipse.equinox.launcher.Main.main(Main.java:1383)
Caused by: java.lang.reflect.InvocationTargetException
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:421)
at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507)
at org.eclipse.ui.internal.progress.ProgressMonitorJobsDialog.run(ProgressMonitorJobsDialog.java:275)
at org.eclipse.ui.internal.progress.ProgressManager$5.run(ProgressManager.java:960)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.ui.internal.progress.ProgressManager.busyCursorWhile(ProgressManager.java:995)
at org.eclipse.ui.internal.progress.ProgressManager.busyCursorWhile(ProgressManager.java:970)
at org.knime.workbench.help.intro.NewProjectWizardIntroAction.run(NewProjectWizardIntroAction.java:93)
... 38 more
Caused by: java.lang.RuntimeException: org.eclipse.core.runtime.CoreException: Resource "KNIME_project" does already exist.
at org.knime.workbench.help.intro.NewProjectWizardIntroAction$1.run(NewProjectWizardIntroAction.java:105)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
Caused by: org.eclipse.core.runtime.CoreException: Resource "KNIME_project" does already exist.
at org.knime.workbench.ui.wizards.project.NewProjectWizard.throwCoreException(NewProjectWizard.java:252)
at org.knime.workbench.ui.wizards.project.NewProjectWizard.doFinish(NewProjectWizard.java:183)
at org.knime.workbench.help.intro.NewProjectWizardIntroAction$1.run(NewProjectWizardIntroAction.java:101)
... 1 more
This error indicated that you are creating a new KNIME workflow from the intro page but a flow with this name (KNIME_project) already exists. I don't know why but you can circumvent this problem by closing the intro page instead of clicking on the "Open Workbench" icon. We should handle this more gracefully, though.
!ENTRY org.eclipse.core.resources 2 10035 2011-10-07 14:45:01.676
!MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.
please find attached the knime.log part regarding the last use, even though it seems ok to me