title: Reasons for "no more handles"
body: <p>For our SWT-based application we've got certain different SWT crash reports where SWT crashes with "no more handles" errors. This only happens for very few people and sometimes in a very early stage of launching the application. A typical stacktrace of the very early application state looks like this:</p>
  
  <pre><code>Caused by: org.eclipse.swt.SWTError: No more handles
      at org.eclipse.swt.SWT.error(SWT.java:4467)
      at org.eclipse.swt.SWT.error(SWT.java:4356)
      at org.eclipse.swt.SWT.error(SWT.java:4327)
      at org.eclipse.swt.widgets.Widget.error(Widget.java:476)
      at org.eclipse.swt.widgets.TaskBar.createHandle(TaskBar.java:103)
      at org.eclipse.swt.widgets.TaskBar.&lt;init&gt;(TaskBar.java:96)
      at org.eclipse.swt.widgets.Display.getSystemTaskBar(Display.java:2567)
      ...
  </code></pre>
  
  <p>We already have tested our application and under normal conditions it does not leak any resources (fonts, colors, images, GCs, ...), the values in the Windows Task Manager (Handles, USER Objects, GDI Objects, ...) are only in the top third, but often not the top most ones.</p>
  
  <p>What reasons could cause such problems - could it be a machine with a lot of applications running, other possibly debugged applications leak massive resources, what else? What information, e.g. output of "tasklist.exe" I need to request from the users to get a clue for a possible reason?</p>