VLCKit crash on Mojave / Big Sur when compiled with Xcode 15.0
Hi!
I've been using VLCKit-3.6.0b4 all summer with excellent results, and a couple weeks ago I tried updating to VLCKit-3.6.0b10, which also worked really well in all my tests.
There's something to say about my testing procedure
As soon as my app embedding VLCKit-3.6.0b10 launches on Big Sur and Mojave on Intel Macs, it crashes.
Attached you can find 2 crash reports, one from Big Sur I received from a User and the other after I was able to reproduce the issue on Mojave myself; both are symbolicated, but the symbols of my app do not seem to be "involved" in the crash.
Just for skimming this issue, here's the relevant part extracted from one of the attachments:
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
...
Crashed Thread: 10
...
Thread 10 Crashed:
0 ??? 000000000000000000 0 + 0
1 org.videolan.vlckitframework 0x00000001030eefd8 Connect(demux_t*) + 360
I am fairly convinced the issue lies with VLCKit-3.6.0b10 because if I swap out that framework and revert to VLCKit-3.6.0b4 without changing anything else in my code, the app does not crash on launch anymore (tested on the same Big Sur machine by my User and on a Mojave machine by me); when I re-add VLCKit-3.6.0b10, the crash on launch returns.
I don't find the attached crash reports particularly useful, to be honest, but maybe the Connect(demux_t*)
symbol in the crashing thread of both reports is enough to point in the right direction.
For me personally, this is far from an urgent issue: I have reverted the released app back to VLCKit-3.6.0b4 and Apple's App Review approved the update in brilliantly quick time (16 minutes from submission to approval, hats off).
But I still thought it made sense to inform you of the issue, so that it can be evaluated and tested more; please, let me know if I can help in any way, and as always thanks for all your work!
Attached crash reports: