> If you click on the Run button, ie the arrow on the toolbar, but
> don't release your mouse button, the CPU usage in Windows Task
> Manager goes up to 100%.
Cool! This could be VEE waiting for a WM_LBUTTONUP message, although that's
not standard behavior.
> I seem to remember that error output pins could be a source of
> resouce consumption / memory leak.
True - memory leak anyway. But it's not enough memory to worry about until
you get to hundreds of thousands or even millions of pings on error pins.
-SHAWN-
---
You are currently subscribed to vrf as: rsb@soco.agilent.com
To subscribe send a blank email to "join-vrf@it.lists.it.agilent.com".
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
> don't release your mouse button, the CPU usage in Windows Task
> Manager goes up to 100%.
Cool! This could be VEE waiting for a WM_LBUTTONUP message, although that's
not standard behavior.
> I seem to remember that error output pins could be a source of
> resouce consumption / memory leak.
True - memory leak anyway. But it's not enough memory to worry about until
you get to hundreds of thousands or even millions of pings on error pins.
-SHAWN-
---
You are currently subscribed to vrf as: rsb@soco.agilent.com
To subscribe send a blank email to "join-vrf@it.lists.it.agilent.com".
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".