Author Topic: Eclipse hangs after crash  (Read 27564 times)

chris

  • Junior Community Member
  • Posts: 3
  • Hero Points: 0
Eclipse hangs after crash
« on: February 08, 2008, 12:05:13 am »
I can no longer start Eclipse because it just hangs when loading "com.slickedit.eclipse.plugin".

This has happened a couple of times before and is always due to Eclipse crashing.  The only way I have found to recover is to rebuild my workspace, and then copy whatever files I had changed into the new workspace.

Is there a fix for this, or a better way of recovering from it?  I am using version 3.3.1

Ryan

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 986
  • Hero Points: 77
Re: Eclipse hangs after crash
« Reply #1 on: February 08, 2008, 03:18:15 pm »
Quote
Is there a fix for this

If I get some more information about your Eclipse crashes and then the subsequent startup hang, I might be able to diagnose what's going on.  Also, are you on Windows or Linux? 

Is your editor still in a state where Eclipse is hanging on startup?  If so, I'd like to see your Eclipse error log file for your workspace, which is located at workspace_dir/.metadata/.log

I'd also like to see what tracing info we can get from the plug-ins as they are starting up (and hanging, apparently).  Open a command line tool and navigate to your Eclipse directory.  You are going to manually launch Eclipse with the -vstrace option:

  • Windows - .\eclipse.exe -vm java.exe -vstrace.
  • Linux - ./eclipse -vstrace.  Or, if you are starting with the eclipse-se.sh script, just open the script and find where it launches eclipse at the bottom, and add the -vstrace option.

Copy the output to a file.  You can either send both the .log file and this info to support@slickedit.com (and reference this thread), or just reply here and attach them to your post.  If your editor is not in a state where it is hanging on startup, clear out the .log file, and then follow these same steps once you encounter the problem again.

Quote
or a better way of recovering from it?

Normally with something like this I would have you try renaming your SlickEdit configuration directory to start with a default config, but since when you create a workspace the plug-ins load fine, this is probably not the problem.  SlickEdit does store the tag files with the workspace...you can try nuking these (or moving them away) to see if they are getting corrupted and causing the problem.  They are located at workspace_dir/.metadata/.plugins/com.slickedit.core/tagfiles.

- Ryan

chris

  • Junior Community Member
  • Posts: 3
  • Hero Points: 0
Re: Eclipse hangs after crash
« Reply #2 on: February 11, 2008, 08:51:14 pm »
Hi Ryan,

Here's the info ...

workspace_dir/.metadata/.log:
Code: [Select]
!SESSION 2008-01-22 10:02:32.734 -----------------------------------------------
eclipse.buildId=M20071023-1652
java.version=1.6.0_03
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments:  -os win32 -ws win32 -arch x86

This is a continuation of log file C:\Eclipse\.metadata\.bak_0.log
Created Time: 2008-01-22 14:04:10.281

!ENTRY org.eclipse.ui.workbench 4 0 2008-01-22 14:04:10.281
!MESSAGE WARNING: Prevented recursive attempt to activate part com.slickedit.eclipse.plugin.editor while still in the middle of activating part org.eclipse.ui.navigator.ProjectExplorer
!STACK 0
java.lang.RuntimeException: WARNING: Prevented recursive attempt to activate part com.slickedit.eclipse.plugin.editor while still in the middle of activating part org.eclipse.ui.navigator.ProjectExplorer
at org.eclipse.ui.internal.WorkbenchPage.setActivePart(WorkbenchPage.java:3352)
at org.eclipse.ui.internal.WorkbenchPage.activate(WorkbenchPage.java:611)
at com.slickedit.javasup.selection.SelectionHelper.handle(SelectionHelper.java:43)
at com.slickedit.selection.SelectionHelperFactory.handleSelection(SelectionHelperFactory.java:29)
at com.slickedit.selection.VSESelectionListener.selectionChanged(VSESelectionListener.java:37)
at org.eclipse.ui.internal.AbstractSelectionService.fireSelection(AbstractSelectionService.java:156)
at org.eclipse.ui.internal.AbstractSelectionService.setActivePart(AbstractSelectionService.java:282)
at org.eclipse.ui.internal.WorkbenchPagePartList.fireActivePartChanged(WorkbenchPagePartList.java:59)
at org.eclipse.ui.internal.PartList.setActivePart(PartList.java:126)
at org.eclipse.ui.internal.WorkbenchPage.setActivePart(WorkbenchPage.java:3402)
at org.eclipse.ui.internal.WorkbenchPage.requestActivation(WorkbenchPage.java:2946)
at org.eclipse.ui.internal.PartPane.requestActivation(PartPane.java:265)
at org.eclipse.ui.internal.PartPane.handleEvent(PartPane.java:229)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:962)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:943)
at org.eclipse.swt.widgets.Shell.setActiveControl(Shell.java:1273)
at org.eclipse.swt.widgets.Shell.WM_MOUSEACTIVATE(Shell.java:2015)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:3713)
at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:291)
at org.eclipse.swt.widgets.Decorations.windowProc(Decorations.java:1554)
at org.eclipse.swt.widgets.Shell.windowProc(Shell.java:1753)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4364)
at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2260)
at org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:77)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:3760)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4364)
at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2260)
at org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:77)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:3760)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4364)
at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2260)
at org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:77)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:3760)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4364)
at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2260)
at org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:77)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:3760)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4364)
at org.eclipse.swt.internal.win32.OS.CallWindowProcW(Native Method)
at org.eclipse.swt.internal.win32.OS.CallWindowProc(OS.java:2179)
at org.eclipse.swt.widgets.Tree.callWindowProc(Tree.java:1541)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:3760)
at org.eclipse.swt.widgets.Tree.windowProc(Tree.java:5370)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4364)
at org.eclipse.swt.internal.win32.OS.PeekMessageW(Native Method)
at org.eclipse.swt.internal.win32.OS.PeekMessage(OS.java:2769)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3288)
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(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
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)


.\eclipse.exe -vm java.exe -vstrace (all output, and then it hangs):
Code: [Select]
com.slickedit.core: urlEntry for SlickEditCore.jar=bundleentry://496/SlickEditCo
re.jar
com.slickedit.core: path for SlickEditCore.jar=C:/Program Files/SlickEdit Plug-I
n 3.3.1 for Eclipse/eclipse/plugins/com.slickedit.core_3.3.1/SlickEditCore.jar
com.slickedit.core: path=C:/Program Files/SlickEdit Plug-In 3.3.1 for Eclipse/ec
lipse/plugins/com.slickedit.core_3.3.1
com.slickedit.core: Locating plugin: translate slashes = C:\Program Files\SlickE
dit Plug-In 3.3.1 for Eclipse\eclipse\plugins\com.slickedit.core_3.3.1\win
com.slickedit.core: Update File Path is: C:\Program Files\SlickEdit Plug-In 3.3.
1 for Eclipse\eclipse\plugins\com.slickedit.core_3.3.1\win\.upddat
com.slickedit.core: Starting Plugin
com.slickedit.core: Trying to load libraries.
com.slickedit.core: Loading: C:\Program Files\SlickEdit Plug-In 3.3.1 for Eclips
e\eclipse\plugins\com.slickedit.core_3.3.1\win\vsenv.dll
com.slickedit.core: Loading: C:\Program Files\SlickEdit Plug-In 3.3.1 for Eclips
e\eclipse\plugins\com.slickedit.core_3.3.1\win\vseclipse.dll

Rick P.

  • Community Member
  • Posts: 6
  • Hero Points: 0
Re: Eclipse hangs after crash
« Reply #3 on: January 29, 2010, 11:45:53 pm »
Ryan,

Did you get a resolution to this problem?  I am experiencing the same problem and share in your frustration.  I am using SlickEdit Core 3.5.

Thanks,
Rick

Ryan

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 986
  • Hero Points: 77
Re: Eclipse hangs after crash
« Reply #4 on: February 01, 2010, 04:32:32 pm »
Hey Rick,

You might want to start a new thread in the SlickEdit Core forums, as this is an old, archived forum.  Also, I looked through the .log file and I've never seen this error before.

As a sanity check, can you post the information from Help > About SlickEdit Core?  It's weird but the offending method referenced in the .log file does not exist in Core 3.5...but it did in Core 3.4.  Just to make sure you are running 3.5 I would like to see that information, feel free to take out any information from that dialog that you don't want posted, I just want to see the version.

If it turns out you don't have 3.5, you probably want to uninstall your version of the plug-in and install Core 3.5, as this is probably what you want anyways.

If you are running 3.5 (or switching to 3.5 doesn't fix the problem), have you tried starting a new workspace to try and get around the problem?  I think this might work in your case.  Instead of starting Eclipse with your old workspace, start a new one and add your projects.  SlickEdit should automatically build a tag file for each project when it is loaded, and you can check Tools > Tag Files to make sure.  There should be a tag file listed for each project in your workspace, and when you select the project tag file in the left pane you should see all the files in the project in the right pane.  If it doesn't look like all the projects got tagged, manually retag the workspace at Tools > Retag Workspace.

Let me know if you can restart Eclipse without issue now, or if the problem still persists.  I'll keep looking into the error in the .log file, there is one NPE I discovered (which is easy to fix) but I don't think that is what is at the root of this issue.  Thanks for the report.

- Ryan