Reference Leak in "Queue"

[James_W]

Hi all,

I know that some of you use the JKI VI Tester.
I was curious to validate that my tests has no Reference leaks in them, so I ran the DETT tool alongside the VI Tester and I'm getting some interesting results.
I'm getting reference leaks in the startup VIs ... It's telling me the source is Queue :0x..........
(I think it's where I'm using named queues) and releasing them and force destroying them in the teardown, but moving the release into the startup doesn't remove the issue, putting a DDS around the code doesn't remove the issue either. I'm absolutle foxed.
- I'm not sure it's Classes or Queues that's causing the issue here yet.
Anyone seen any issues with reference leaks

If I run the test code for a module on it's own it seems to work, but if I run other code first, it hangs LV until I taskkill. I don't know if these are related (This is why I've got DETT open to try and find the issue - I've already found a bug with the JKI source code)

Anyone got any ideas please?

Cheers

James

[James_W · Accepted solution]

😩
Found it...
Was:
1) a Queue I'd forgotten to initialise for testing.
2) another that I found leaking references due to bad naming and failure to close references.

(Although it seems the JKI VI Tester leaks too)