LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Open Event Handles...

When i look under process explorer, labview is generating an event handle per event that the event handling case has registered (i.e, if you have an value change registered for a boolean, then it creates a new handle to this event each time the event is generated...) but somehow it never closes these handles. so my application keeps creating thousands of open handles... (i monitor mouse movements..) is there a way to close these handles???
0 Kudos
Message 1 of 3
(2,705 Views)
Actually, i thought each of the open handles were handles that were generated during events but that is not true. as soon as they are handled, those get closed... but for some reason my labview exe has 4700 + handles open at any given time. i dont know why. does anyone know why these many windows handles are open at any given time??
0 Kudos
Message 2 of 3
(2,705 Views)
> Actually, i thought each of the open handles were handles that were
> generated during events but that is not true. as soon as they are
> handled, those get closed... but for some reason my labview exe has
> 4700 + handles open at any given time. i dont know why. does anyone
> know why these many windows handles are open at any given time??

This makes more sense than the event thing. LV events handling doesn't
allocate any system resources other than a bit of space on the stack and
maybe the expansion of some memory resource.

The system handles are all sorts of things, windows, bitmaps, regions,
fonts, pens, and brushes. Most of these are probably bitmaps and icons
that LV loads up so that it can draw the diagram. Up to a few hundred
pens an
d brushes for drawing can be cached. The number of regions
should be pretty small, but there are a couple per window.

Anyway, the LV editor initially loads up the built-in resources, then as
you browse the palettes you might even notice it going to disk the first
time you expose a subMenu. Each time it does this some more resources
are loaded, which can make it look like a leak, but it really isn't.

So, if you determine that this really is leaking, please report how you
get it to leak, but otherwise, just chalk this up to being a graphical
language where plus and minus aren't two monospaced characters in a
font, but rather a masked icon requiring system bitmaps.

Greg McKaskle
0 Kudos
Message 3 of 3
(2,705 Views)