Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 333628

Summary: The UI does not open new windows and eclipse wont close
Product: [Eclipse Project] Platform Reporter: Hugo <hugooooo>
Component: SWTAssignee: Platform-SWT-Inbox <platform-swt-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: critical    
Priority: P3 CC: eclipse.felipe, grant_gayed, prakash, remy.suen
Version: 3.6   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Attachments:
Description Flags
the eclipse log none

Description Hugo CLA 2011-01-06 03:26:55 EST 
Build Identifier: org.eclipse.ui 4 0 2011-01-06 09:15:35.468

At random moments, not reproducible,
the UI does not open new windows and
when trying to close eclipse it signals a negative array length
and does not close. I have to kill the process by hand.

Part of the log:
!SESSION 2011-01-05 17:58:14.515 -----------------------------------------------
eclipse.buildId=M20100909-0800
java.version=1.6.0_21
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=fr_FR
Command-line arguments:  -os win32 -ws win32 -arch x86

!ENTRY org.eclipse.ui 4 0 2011-01-06 09:15:35.468
!MESSAGE Error occurred during status handling
!STACK 0
org.eclipse.swt.SWTError: Cannot get the enabled state

Reproducible: Always
Comment 1 Hugo CLA 2011-01-06 03:28:12 EST 
Created attachment 186150 [details]
the eclipse log
Comment 2 Remy Suen CLA 2011-01-06 07:51:10 EST 
Seems like win32 gone crazy. SWT, any comments as to why the MenuItem wouldn't be able to retrieve its enablement state?
Comment 3 Felipe Heidrich CLA 2011-01-07 17:16:07 EST 
(In reply to comment #2)
> Seems like win32 gone crazy. SWT, any comments as to why the MenuItem wouldn't
> be able to retrieve its enablement state?

The OS got in a bad state, somehow (leak, memory corruptin, etc).

I need steps to reproduce this, otherwise it will be too hard to find the root of the problem.
Comment 4 Grant Gayed CLA 2013-06-27 10:27:56 EDT 

*** This bug has been marked as a duplicate of bug 321554 ***