title: Overcoming Windows User Object Handle Limit
body: <p>I'm looking for advanced strategies for dealing with User Object Handle limits when building heavy-weight windows interfaces.  Please explain how you overcame or bypassed this issue using SWT or direct Windows GUI APIs.  The only thing I am not interested in is strategies to optimize widget usage as I have done this extensively and it does not solve the problem, only makes it less likely.</p>
  
  <p>My Situation:<br>
  I have an SWT based GUI that allows for multiple sessions within the same parent shell and within each session their are 3 separate places where a list of user generated comments are displayed.  As a user opens multiple sessions and pulls data that populates those lists, the number of user object handles can increase dramatically depending on the number of comments.</p>
  
  <p>My current solutions:<br>
  1. I page the comments by default thereby limiting the number of comment rows in each session, but due to management demands, i also have what is effectively a "View All" button which bypasses this completely.<br>
  2. I custom draw all non-editable information in each row.  This means each row utilizes only 2 object handles.<br>
  3. I created JNI calls which query the OS for the current usage and the Max usage.  With this i can give indications to users that a crash is imminent.  Needless to say, they ignore this warning.</p>