Site navigation

Objc warnings at exit since catalina switch

#1

All my juce apps with juce6 now print this at exit:

objc[42970]: objc_disposeClassPair: class 'JUCEWindow_7654d7c572cb2def' still has subclasses, including 'NSKVONotifying_JUCEWindow_7654d7c572cb2def'!
objc[42970]: objc_disposeClassPair: class 'JUCEWindow_7654d7c572cb2def' still has subclasses, including 'NSKVONotifying_JUCEWindow_7654d7c572cb2def'!
objc[42970]: objc_disposeClassPair: class 'JUCEView_b11f4fbe71056da2' still has subclasses, including 'NSKVONotifying_JUCEView_b11f4fbe71056da2'!
objc[42970]: objc_disposeClassPair: class 'JUCEView_b11f4fbe71056da2' still has subclasses, including 'NSKVONotifying_JUCEView_b11f4fbe71056da2'!

i’m pretty sure i’m releasing my objects at the end, and ASAN is confirming.

Anyone got these ? Any idea on how to get rid of them ?

#2

Previous thread on this topic: Warning messages on startup

#3

annoying. i wonder why only juce get those. might be because of the objc helpers custom dispose pairs?

#4

found this, maybe it can inspire some ideas https://www.cocoawithlove.com/2010/01/getting-subclasses-of-objective-c-class.html

#5

it seems to be those static ObjCClass objects that are destroyed at static finalization.

NSView* NSViewComponentPeer::createViewInstance()
{
    static JuceNSViewClass cls;
    return cls.createInstance();
}

NSWindow* NSViewComponentPeer::createWindowInstance()
{
    static JuceNSWindowClass cls;
    return cls.createInstance();
}