Hi,
I’m in problems. All the projects I compile when I close them after running finish with this message:
JUCE Assertion failure in juce_LeakedObjectDetector.h:104
I am lost because I don’t know what is in my computer that is causing this problem.
I am using Visual Studio 2022 and the last version of JUCE.
Thanks in advance
I occasionally get this error, then it goes away. I never use Accessibility features. I think someone from Juce looked into it, but could not find any leads. The reason for it going away might be a clean rebuild, rebooting the computer, or it just stops all by itself. I’d like to know why it happens, yet reproducing the error seems impossible.
I noticed that too. Windows 10. In any kind of project. After a full reboot it disappears and does not appear again until something specific happens.
Haven’t tested it in detail but it could be related to Windows popup messages or other 3rd party apps that use a notification overlay. For example using a keyboard hotkey to skip a song in a music app (like Spotify) often shows a small overlay of the current track with buttons.
So I reduced it to “using Spotify overlay” and at some point it reappeared. Could it be an overlay that unexpectedly interrupts some temporary accessibility handle that then dangles and leaks?
hI,
the rebooting systems didn’t solve the problem. I suspect it has to do with some update of the windows library and my candidate is UIautomationcore.dll. It is dated 03/28//25. In fact it loads when I run the apps even though I don’t use Accessibility at any time.
This issue happens to me with both JUCE 6 and JUCE 8 and until about 6 months ago I had never had this problem. Therefore, my suspicions are directed to Windows (libraries, runtime VS…).
A curious thing is that if I set a breakpoint somewhere in the source code of Juce_Windowing_windows.cpp, specifically in the destructor of HWNDComponentPeer, the exception does not occur
In my case, there is no need to interact with the app, simply opening and closing it causes the problem.
This happens with Demorunner app, ArpegiatorTutorial, my app and so on but I think this issue happens with all project.
If setting a breakpoint stops the error, then it might be to do with timing.
A thread not cleaned up properly yet?
Yes, what you says is very probably and related to the UIautimationcore.dll.
Any way, I’m tranquil because the bug is not in my application and it has not memory leaks
