Jump to content

Memory Leak in "Current VIs Parents Ref.vi"

Recommended Posts

This thread was manually moved from OpenG to LAVA.

The Current VIs Parents Ref.vi opens a reference to a VI and doesn't close it (obviously, because otherwise the ref in the output would not be valid anymore). I think however the help should note that the returned ref should be closed by the caller after he's done with it.

When occasionally calling this VI in your app, it shouldn't be a real problem, but I recently had an application which seemed to have a memory leak, and after letting the Desktop Execution Trace Toolkit take a peek at it, I found that it was caused by Current VIs Parents Ref being called somewhere in the call-chain of a very tight loop (20ms). Closing the ref when done with it fixed this.

Not really a bug this, but expected behaviour that should be clearly noted in the help I think, hence the post here instead of bugs forum.

This was noted in LV2010SP1 btw.

Link to comment
  • 4 months later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...

Important Information

By using this site, you agree to our Terms of Use.