<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en"><title>Recent changes to 115: hang on workspace load after crash</title><link href="http://sourceforge.net/p/eclipsefp/backlog/115/" rel="alternate"></link><id>http://sourceforge.net/p/eclipsefp/backlog/115/</id><updated>2010-05-24T14:08:57Z</updated><entry><title>hang on workspace load after crash</title><link href="http://sourceforge.net/p/eclipsefp/backlog/115/" rel="alternate"></link><updated>2010-05-24T14:08:57Z</updated><published>2010-05-24T14:08:57Z</published><author><name>Michal Konečný</name><uri>http://sourceforge.net/u/mikkonecny/</uri></author><id>http://sourceforge.net6c71e20bf3f7b73a3806150b174042cdade2a993</id><summary type="html">I observed that every time when I open Eclipse with a workspace that contains several Haskell projects \(using eclipseFP 1.110.0\) 
after a system crash, it stops for at least 1-2 minutes on the splash stuck on "Loading Workspace" before opening
the workspace.

The last time it happened, the splash screen keeps getting stuck on at this state for several hours and then I gave up.  
The workspace log from around the time when I tried start up says:

\!ENTRY org.eclipse.osgi 2 0 2010-05-24 10:31:26.182
\!MESSAGE While loading class "net.sf.eclipsefp.haskell.ui.internal.editors.haskell.text.LiterateHaskellPartitionScanner", thread "Thread\[main,6,main\]"
timed out waiting \(5000ms\) for thread "Thread\[Worker-5,5,main\]" to finish starting bundle "net.sf.eclipsefp.haskell.ui\_1.110.0 \[905\]". To avoid deadl
ock, thread "Thread\[main,6,main\]" is proceeding but "net.sf.eclipsefp.haskell.ui.internal.editors.haskell.text.LiterateHaskellPartitionScanner" may no
t be fully initialized.
\!STACK 0
org.osgi.framework.BundleException: State change in progress for bundle "reference:file:plugins/net.sf.eclipsefp.haskell.ui\_1.110.0.jar" by thread "Wo
rker-5".
at org.eclipse.osgi.framework.internal.core.AbstractBundle.beginStateChange\(AbstractBundle.java:1073\)
\(followed by a long Java exception trace\)

I managed to recover from the situation by first opening the projects in another workspace, which failed with strange results
and then reopening the old workspace, this time with no delay.</summary></entry></feed>