Closed randallpacker closed 3 years ago
Attached is another is another crash log: atemOSC Crash_1.docx
I see the Crash is at Thread 4:
Crashed Thread: 4
Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY
Application Specific Information: dyld: in dlopen_preflight() abort() called atemOSC(31296,0x7000109d2000) malloc: double free for ptr 0x7f84683c8000
And the crash occurred just as a Program Source was changed.
I am using ATEM Software Control version 8.5.3. Mac OS Catalina.
Should I try upgrading to 8.6? Is there a newer version of atemOSC than 4.1 I can try?
Many thanks,
Randall
I just noticed that it is recommended to download atemOSC.debug.zip associated with the version I am using, in order to isolate the crash, but where is this zip file found?
Looks like the issue is with the [NSTextView(NSPrivate) _scrollRangeToVisible:forceCenter:]
function, which I use to always show latest log entry. Looking around the internets now, obviously silly for a log to crash the app. Hoping to find a solution, but if I don't I'll disable log auto-scroll by default to prevent this
The atemOSC.debug.zip
was a note for my future self, but I can't produce it right now since I'm signing and notarizing the app
How long between opening the app and the crash? Hours? Minutes?
Hi Peter,
Wow, logging crash!!
The crash seems to occur anywhere from 5 to 15 minutes depending upon the activity. The logging make sense, since it seems to take a little longer to crash when there is no real-time data coming back from the Hyperdecks.
I tried to prevent feedback but I couldn’t figure out how to stop it without confusing the app.
I can’t thank you enough!!
Randall
From: Peter Steffey @.> Reply-To: SteffeyDev/atemOSC @.> Date: Sunday, March 21, 2021 at 12:30 PM To: SteffeyDev/atemOSC @.> Cc: RANDALL PACKER @.>, Author @.***> Subject: Re: [SteffeyDev/atemOSC] atemOSC 4.1 crashing periodically (#207)
How long between opening the app and the crash? Hours? Minutes?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.
Ok, I emailed you a potential fixed version to test. With crashing that frequently, I'm wondering if the amount of text in the log is what causes the issue to manifest.
To all,
I got the same issue. 4.1 crashes within 5 minutes after using some fader movements for audio channels on my ATEM Mini Extreme. (Using OSCulator with some MIDI data scaling). First beachballing, and than the imminent crash. In the beachballing state it still sends OSC messages. It seems like buffers are filling up too fast.
It the sluggishness of fader movements in the ATEM SC the ATEM software itself?
Thanks for your amazing work.
I actually have a fix for this ready, I'll try to release this weekend.
Great! I will test it and report as soon as I can.
Ok, fixed in 4.1.4
Greetings all:
I am now using atemOSC 4.1 with all cylinders firing, including two ATEM HD switchers, 3 Hyperdecks, and pretty much all the various control parameters. It's working quite well, it's really a great piece of work Peter!
However, I am experiencing occasional crashes. Here is the Mac OS crash log. atemOSC Crash.docx
I am not very good at reading crash logs but it appears it may be the Apple Connection Kit I have connected to my iMac Pro, where the atemOSC software is running. I have the ATEM software Control running on a different computer, not sure if that matters. I still haven't updated all of my OSC commands in VDMX, but I'm not not sure if that could be an issue. I am also getting a steady stream of feedback from the Hyperdecks while they are running.
When atemOSC crashes, I get the Apple crash report, and am able to reopen and resume working order.
I am curious if there are any insights on this crash issue.
Many thanks,
Randall