Bug 327498 - [Workbench] On start, often get msg that Workbench settings cannot be read and are reset
Summary: [Workbench] On start, often get msg that Workbench settings cannot be read an...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.5.2   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-11 22:33 EDT by Jeffrey Wexler CLA
Modified: 2019-09-06 15:38 EDT (History)
2 users (show)

See Also:


Attachments
Eclipse log file. See 2010-10-12 09:01:39.015 for eclipse launch with bug (914.63 KB, text/plain)
2010-10-12 22:38 EDT, Jeffrey Wexler CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jeffrey Wexler CLA 2010-10-11 22:33:47 EDT
Build Identifier: 20100218-1602

I use the JBoss Seam perspective and the Debug perspective and customize the views in them and their locations. I switch between using each of the two perspectives. Very often, after having shutdown Eclipse (normally) and later start it again (including after the computer has been shutdown and later booted), I get an error that the workspace settings cannot be read and thus are being reset. I then have to re-customize both of the perspectives all over again.
OS is Ubuntu 10.04 Lucid 64-bit. Locale is Japanese. CPU is 64-bit AMD Turion X2 on a HP TouchSmart tx2 laptop. Jvm is java-6-sun-1.6.0.20, 64-bit.
Please fix as this bug can get to be frustrating and time consuming.
Thank you

Reproducible: Sometimes

Steps to Reproduce:
1.Customize the JBoss Seam perspective views and Debug perspective selected views and their locations.
2.Use Eclipse for a while.
3.After several times of starting and stopping eclipse and shutting down and booting the laptop, this often happens.
Comment 1 Jeffrey Wexler CLA 2010-10-11 23:05:08 EDT
I added and use the LogWatcher plugin. Not sure if this may be involved in the cause.

I also have the VirtualWordWrap plugin and JRebel plugin (version 2) from Zeroturnaround.com.
Comment 2 Paul Webster CLA 2010-10-12 09:09:25 EDT
When you get that message, is there anything in your logs?  <workspace>/.metadata/.log.  Please attach.

PW
Comment 3 Jeffrey Wexler CLA 2010-10-12 22:38:08 EDT
Created attachment 180717 [details]
Eclipse log file. See 2010-10-12 09:01:39.015 for eclipse launch with bug

Shutdown of eclipse completed at just after 7am on 2010-10-12. Last timestamp in log for that timeframe was 2010-10-12 07:07:01.991.

Then shut down computer. Then booted computer and eclipse at around 9am on 2010-10-12. First timestamp in log for that timeframe was 2010-10-12 09:01:39.015. (2 lines below the 7am one.)
Comment 4 Jeffrey Wexler CLA 2010-10-13 21:15:08 EDT
I am fairly certain that upon the close of the workspace at the 2010-10-12 7am time, that there was a message saying that the workspace was being compressed and that the shutting down of eclipse took longer than usual when the workspace is only saved. Perhaps, the bug is related to that compress process.
Comment 5 Lyle Ziegelmiller CLA 2010-11-12 17:10:01 EST
I've been having this problem lately also, or at least one similar. All of a sudden, Eclipse started having a lot of problems repainting the screen. I tried minimizing and restoring it, but that didn't help. There are large black regions in the screen (my desktop is black). When I selected a bunch of text, that portion of the window became readable, more or less. But the whole thing was still in a state of chaos. When I exited Eclipse and restarted it, I got an error pop-up window which read, "Unable to read workbench state. Workbench UI layout will be reset. Graphic is disposed". This has happened several times now recently.

The only thing I've done differently since right before this all started was to install the TPTP profiling tool - see http://www.eclipse.org/articles/Article-TPTP-Profiling-Tool/tptpProfilingArticle.html.

I'm using:
Eclipse IDE for Java Developers

Version: Helios Service Release 1
Build id: 20100917-0705


On Windows Vista - what ever the latest service pack is.

!ENTRY org.eclipse.jdt.debug 4 125 2010-10-13 10:44:47.091
!MESSAGE Internal error logged from JDI Debug: 
!STACK 1
org.eclipse.debug.core.DebugException: Invalid stack frame
	at org.eclipse.jdt.internal.debug.core.model.JDIStackFrame.getUnderlyingStackFrame(JDIStackFrame.java:1010)
	at org.eclipse.jdt.internal.debug.core.model.JDIStackFrame.getUnderlyingThisObject(JDIStackFrame.java:700)
	at org.eclipse.jdt.internal.debug.core.model.JDIStackFrame.getThis(JDIStackFrame.java:1058)
	at org.eclipse.jdt.internal.debug.ui.JavaDebugHover.getHoverInfo2(JavaDebugHover.java:328)
	at org.eclipse.jdt.internal.ui.text.java.hover.BestMatchHover.getHoverInfo2(BestMatchHover.java:129)
	at org.eclipse.jdt.internal.ui.text.java.hover.JavaEditorTextHoverProxy.getHoverInfo2(JavaEditorTextHoverProxy.java:82)
	at org.eclipse.jface.text.TextViewerHoverManager$4.run(TextViewerHoverManager.java:166)
!SUBENTRY 1 org.eclipse.jdt.debug 4 100 2010-10-13 10:44:47.092
!MESSAGE Invalid stack frame

!ENTRY org.eclipse.ui 4 4 2010-10-13 12:58:07.160
!MESSAGE Plug-in 'org.eclipse.tptp.monitoring.instrumentation.ui' contributed an invalid Menu Extension (Path: 'btmSourceMenu' is invalid): org.eclipse.tptp.monitoring.instrumentation.ui.CbeExceptionAddAction2

!ENTRY org.eclipse.ui 4 4 2010-10-13 12:58:07.160
!MESSAGE Plug-in 'org.eclipse.tptp.monitoring.instrumentation.ui' contributed an invalid Menu Extension (Path: 'btmSourceMenu' is invalid): org.eclipse.tptp.monitoring.instrumentation.ui.CbeEntryExitAddAction

!ENTRY org.eclipse.ui 4 4 2010-10-13 12:58:07.161
!MESSAGE Plug-in 'org.eclipse.tptp.trace.arm.ui' contributed an invalid Menu Extension (Path: 'btmSourceMenu' is invalid): org.eclipse.tptp.trace.arm.ui.ArmAddAction

!ENTRY org.eclipse.ui 4 0 2010-10-13 12:58:12.690
!MESSAGE Unhandled event loop exception
!STACK 0
org.eclipse.swt.SWTException: Graphic is disposed
	at org.eclipse.swt.SWT.error(SWT.java:3777)
	at org.eclipse.swt.SWT.error(SWT.java:3695)
	at org.eclipse.swt.SWT.error(SWT.java:3666)
	at org.eclipse.swt.graphics.GC.setBackground(GC.java:3936)
	at org.eclipse.swt.custom.StyledTextRenderer.drawLine(StyledTextRenderer.java:367)
	at org.eclipse.swt.custom.StyledText.handlePaint(StyledText.java:5310)
	at org.eclipse.swt.custom.StyledText$7.handleEvent(StyledText.java:4878)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1027)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1012)
	at org.eclipse.swt.widgets.Composite.WM_PAINT(Composite.java:1323)
	at org.eclipse.swt.widgets.Control.windowProc(Control.java:3842)
	at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:337)
	at org.eclipse.swt.widgets.Display.windowProc(Display.java:4541)
	at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
	at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2371)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3420)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2384)
	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2348)
	at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2200)
	at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:495)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:490)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)
	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:386)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
	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:549)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1236)

!ENTRY org.eclipse.ui 4 4 2010-10-13 13:02:12.598
!MESSAGE Plug-in 'org.eclipse.tptp.monitoring.instrumentation.ui' contributed an invalid Menu Extension (Path: 'btmSourceMenu' is invalid): org.eclipse.tptp.monitoring.instrumentation.ui.CbeExceptionAddAction2

!ENTRY org.eclipse.ui 4 4 2010-10-13 13:02:12.599
!MESSAGE Plug-in 'org.eclipse.tptp.monitoring.instrumentation.ui' contributed an invalid Menu Extension (Path: 'btmSourceMenu' is invalid): org.eclipse.tptp.monitoring.instrumentation.ui.CbeEntryExitAddAction

!ENTRY org.eclipse.ui 4 4 2010-10-13 13:02:12.599
!MESSAGE Plug-in 'org.eclipse.tptp.trace.arm.ui' contributed an invalid Menu Extension (Path: 'btmSourceMenu' is invalid): org.eclipse.tptp.trace.arm.ui.ArmAddAction

!ENTRY org.eclipse.ui 4 4 2010-10-13 13:02:22.342
!MESSAGE Plug-in 'org.eclipse.tptp.monitoring.instrumentation.ui' contributed an invalid Menu Extension (Path: 'btmSourceMenu' is invalid): org.eclipse.tptp.monitoring.instrumentation.ui.CbeExceptionAddAction2

!ENTRY org.eclipse.ui 4 4 2010-10-13 13:02:22.342
!MESSAGE Plug-in 'org.eclipse.tptp.monitoring.instrumentation.ui' contributed an invalid Menu Extension (Path: 'btmSourceMenu' is invalid): org.eclipse.tptp.monitoring.instrumentation.ui.CbeEntryExitAddAction

!ENTRY org.eclipse.ui 4 4 2010-10-13 13:02:22.343
!MESSAGE Plug-in 'org.eclipse.tptp.trace.arm.ui' contributed an invalid Menu Extension (Path: 'btmSourceMenu' is invalid): org.eclipse.tptp.trace.arm.ui.ArmAddAction

!ENTRY org.eclipse.ui 4 0 2010-10-13 13:02:28.780
!MESSAGE Unhandled event loop exception
!STACK 0
Comment 6 Eclipse Webmaster CLA 2019-09-06 15:33:01 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
Comment 7 Eclipse Webmaster CLA 2019-09-06 15:38:07 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.