DemoRunner: Leaked AccessibilityNativeHandle object

[benstaton]

Hi all,

We have a couple of JUCE apps in development, and in both apps we get a leak assert on closing the app while running in the Visual Studio debugger. It happens maybe 40% of the time. I’d assumed it was something we’re doing wrong, but I can also get it to happen in DemoRunner (v6.1.2):

1. Open DemoRunner in the VS debugger
2. Select “Browse Demos”
3. Select “GUI”
4. Select “Menus Demo”
5. Click to open the “Menu Position” menu, and leave it open
6. Click the “X” button in the window title bar to close the app
7. JUCE LeakedObjectDetector asserts

If this is reproducible for others, we would appreciate a fix ASAP.

Tagging @ed95 since it potentially involves the new JUCE 6.1 accessibility stuff.

Many thanks!
Ben

Edit: I tried HeavyweightLeakedObjectDetector in our apps, which gave me a stack but I didn’t find it particularly useful in this case. Feel free to DM me if you want the stacks though (I have 3 so far from our apps).

[benstaton]

I somehow neglected to mention that the leaked object is a juce::AccessibilityNativeHandle, and that it happens on Windows

*** Leaked objects detected: 1 instance(s) of class AccessibilityNativeHandle
JUCE Assertion failure in juce_LeakedObjectDetector.h:92

[ed95]

Thanks for reporting. This should be fixed on develop now:

Windows Accessibility: Only send window open/close events for main application windows to fix COM ref-counting leak

[benstaton]

Thank you, @ed95!