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

Bug 348752

Summary: org.eclipse.swt.SWTError: No more handles MESSAGE Unhandled event loop exception
Product: [Eclipse Project] Platform Reporter: tolwyn85
Component: SWTAssignee: Platform-SWT-Inbox <platform-swt-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: pwebster
Version: 3.6.1   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug
Attachments:
Description Flags
Logfile from workspace
none
File that crashes eclipse none

Description tolwyn85 CLA 2011-06-08 10:28:38 EDT 
Build Identifier: 20100917-0705

Workspace cannot be opened after File in UTF-8 Encoding is opened.

File request006.txt contains random 100000 characters out of the Unicode Range 0x20 to 0xD7FF in ONE Line. (no carriage return/ line feed before)

The file is saved as UTF-8. 
Eclipse fails to open it and the GUI crashes with Error Description:

org.eclipse.swt.SWTError: No more handles

Eclipse process is still alive and has to shut down manually. 

It is not possible to reopen the workspace, because Eclipse tries to open the file again and crashes. 

Workaround: Change of workbench.xml :: remove the line with the corresponding file. 

Reproducible: Always

Steps to Reproduce:
1.Create folder and file "C:/workspace/src/request006.txt"
2.Insert content into file as described in "Details"
3.Open Eclipse with above workspace 
4.Create new Java Project and import the files from Folder
5.Check the Encoding of the File "request006.txt" - it should be CP1252
6.Open the file - everythings ok
7.Change the Encoding to UTF
Comment 1 tolwyn85 CLA 2011-06-08 10:30:44 EDT 
Created attachment 197605 [details]
Logfile from workspace
Comment 2 tolwyn85 CLA 2011-06-08 10:42:15 EDT 
Created attachment 197607 [details]
File that crashes eclipse
Comment 3 Lars Vogel CLA 2019-11-14 03:16:05 EST 
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.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.