Eclipse Community Forums: Standard Widget Toolkit (SWT)

Home » Eclipse Projects » Standard Widget Toolkit (SWT) » 'No more handles' SWT Exception

'No more handles' SWT Exception [message #437056]

Fri, 28 May 2004 04:26

Eclipse User

Originally posted by: cbr.teamlog.com

Does anybody could tell me what this exception means :

org.eclipse.swt.SWTError: No more handles

Thanks for feedbacks,

-MaRc

Re: 'No more handles' SWT Exception [message #437057 is a reply to message #437056]

Fri, 28 May 2004 05:14

Eclipse User

Originally posted by: v.j.b

> org.eclipse.swt.SWTError: No more handles

it is most likely that you are using some of the painting functions of SWT,
or some objects like Colors, Images, etc, that you _yourself_ need to
dispose of when no longer used. So, after you're finished with them, call
(objectname).dispose().

The handles are the id's used by the operating system to refer to resources
such as images and windows. In SWT it is obligatory to dispose of those
yourself, instead of relying on the garbage collector (which does not know
of any os resources, afaik).

Re: 'No more handles' SWT Exception [message #437060 is a reply to message #437057]

Fri, 28 May 2004 06:16

Eclipse User

In addition that error may occur when using browser widget or the printer
class on Linux.

> > org.eclipse.swt.SWTError: No more handles

> it is most likely that you are using some of the painting functions of SWT,
> or some objects like Colors, Images, etc, that you _yourself_ need to
> dispose of when no longer used. So, after you're finished with them, call
> (objectname).dispose().

> The handles are the id's used by the operating system to refer to resources
> such as images and windows. In SWT it is obligatory to dispose of those
> yourself, instead of relying on the garbage collector (which does not know
> of any os resources, afaik).

Re: 'No more handles' SWT Exception [message #740284 is a reply to message #437056]

Tue, 18 October 2011 06:44

Eclipse User

This problem can also occur if you perform an intensive ui update operation, such as expanding a tree view. As you delegate the update to the ui thread, it becomes easier to call the, for instance 'expandall' function multiple times, with the risk that the tree is busy with expanding when it gets the following call to do so, etc. It may be wise to prevent this from happening by either introducing a boolean 'updating' to prevent consecutive calls from performing an expand if the thread is busy, or use other means of slowing down the expand calls (e.g. in a separate thread) .

I had this happening when we wanted to visualise a process, with the expand option, but as the process was so fase, the GUI could not keep up

Re: 'No more handles' SWT Exception [message #741723 is a reply to message #740284]

Wed, 19 October 2011 16:50

Eclipse User

You can try this link http: //webcache.googleusercontent.com/search?q=cache:Q2k_tpP_UrEJ:i-proving.ca/space/David%2BJones/blog/2006-06-05_1+/search%3Fhl%3Den%26client%3Dfirefox-a%26hs%3D3SZ%26rls%3Dorg.mozilla:en-GB:official%26q%3D%2Bsite:i-proving.ca%2BDiagnosing%2BHandle%2BLeaks%2Bin%2BSWT/RCP%2BWindows%2BApplications&cd=1&hl=en&ct=clnk
The link may be old but it's informative.

Previous Topic:	Question about "deferred events"
Next Topic:	How to add a separator between two tree items

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Jul 23 15:19:54 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter