Set Cursor (Icon Pict).vi Reference Leaks

[mje]

What's the correct way to set the cursor to a busy state? I'm getting this in the trace execution toolkit when I run my application:

VI: Set Cursor (Icon Pict).vi

Event: Reference Leak

Details: Cursor ID: [some U32 number]

Call Chain: ...LabVIEW.Messaging.2.0.lvlib:View.lvclass:UI.SetBusy.vi>> Set Busy.vi>> Set Cursor (Icon Pict).vi

The SetBusy.vi for me looks like so:

Originally I didn't have the Destroy Cursor.vi calls in there, they are an (unsuccessful) attempt to clean up the reference leaks.

Note the special handling, this method is part of an extensible class representing a view, there's logic in there to handle if the user interface is in a subpanel or not since you can't set the cursor in a subpanel (don't get me started on that one). I'm thinking this might stem from the use of subpanels because I don't have this issue with parts of my application which are stand-alone windows without subpanels. Any ideas?

[mabe]

Hi,

I have found the same leak in LV 8.5 or 8.6 while using the beta version of the Desktop trace toolkit few years ago. At that time I have oppened a service request on this and a CAR was maybe raised but I not sure. I think there is no way to avoid the leak...

[mje]

Thanks, mabe. Indeed, if there's a way to avoid the leak, I have yet to find it. The "good" news is the leak is not cumulative, you get only one leak for each VI that is operated on regardless of how many times you call Set Busy.vi on that VI.

[drjdpowell]

The "good" news is the leak is not cumulative, you get only one leak for each VI that is operated on regardless of how many times you call Set Busy.vi on that VI.

Should that meaningfully be called a “leak” then?