In Mac OS Golden Gate the Topaz Video crashes

konrad.ciecierski · September 16, 2026, 1:47pm

After upgrade of Mac to the Golden Gate OS, the Topaz Video crashes every time I switch the monitor to another computer. After I switch back to mac, the GUI is crashed, the ffmpeg process still remains working and has to be killed manually.

This behavior is repeatable.

domdom · September 16, 2026, 3:23pm

I have experienced this a lot as I was testing macOS beta versions. My current solution is to remove the audio from the video file, then Video AI does not crash. After processing, I add the audio back in.

The crash appears to be associated with a racing condition in the mpv library (this is as far as I can go, need the Topaz team to provide more insights)

github.com/mpv-player/mpv

macOS: SIGSEGV in ao_coreaudio hotplug_cb (null deref in mp_msg_va) on audio device change

opened 01:30PM - 17 Jul 26 UTC

closed 03:36PM - 01 Sep 26 UTC

ToBrich

os:mac

### mpv Information ```bash mpv v0.41.0 Copyright © 2000-2025 mpv/MPlayer/mplay…er2 projects libplacebo version: v7.360.1 FFmpeg version: 8.1.1 (runtime 8.1.2) FFmpeg library versions: libavcodec 62.28.101 (runtime 62.28.102) libavdevice 62.3.101 (runtime 62.3.102) libavfilter 11.14.101 (runtime 11.14.102) libavformat 62.12.101 (runtime 62.12.102) libavutil 60.26.101 (runtime 60.26.102) libswresample 6.3.101 (runtime 6.3.102) libswscale 9.5.101 (runtime 9.5.102) ``` ### Other Information ```text - macOS version: macOS 27.0 (26A5378n) (beta seed) - Source of mpv: Homebrew bottle, mpv 0.41.0 (/opt/homebrew/bin/mpv) - Latest known working version: Unknown - Issue started after the following happened: Started today (2026-07-17). mpv is spawned as a background child process by a third-party player app (fntv, com.qiaokes.fntv) that uses the Homebrew mpv binary as its playback engine. mpv crashed twice today, each time 1-2 minutes after launch, with an identical crash signature. ``` ### Reproduction Steps Not deterministically reproducible on demand, but it happened twice today with an identical crash signature: 1. Run mpv on macOS with ao=coreaudio (in my case mpv is launched by a third-party app as its playback engine and plays a video). 2. While mpv is running, an audio device change occurs (CoreAudio "objects published and died", e.g. a Bluetooth headset connecting/disconnecting or another audio device appearing/disappearing). 3. mpv crashes immediately with SIGSEGV. Both times the crash happened 1-2 minutes after the mpv process started, while mpv's main thread was idle in the AppKit event loop. ### Expected Behavior mpv handles CoreAudio device hotplug notifications gracefully (re-selects the device / emits the hotplug event) without crashing. ### Actual Behavior mpv dereferences a null pointer and dies with SIGSEGV (EXC_BAD_ACCESS, KERN_INVALID_ADDRESS at 0x0) inside the CoreAudio hotplug callback. Crashed thread (dispatch queue "HALC_ProxyNotification Call Listener Queue"): 0 mpv mp_msg_va + 40 1 mpv mp_msg + 28 2 mpv hotplug_cb + 40 3 CoreAudio HALObject::PropertiesChanged(unsigned int, AudioObjectPropertyAddress const*) 4 CoreAudio HALSystem::PropertiesChanged(unsigned int, AudioObjectPropertyAddress const*) 5 CoreAudio HALSystem::ObjectsPublishedAndDied(unsigned int, unsigned int const*, unsigned int, unsigned int const*) 6 CoreAudio HALSystem::AudioObjectsPublishedAndDied(AudioHardwarePlugInInterface**, unsigned int, unsigned int, unsigned int const*, unsigned int, unsigned int const*) 7 CoreAudio HALC_ShellPlugIn::ProxyObject_PropertiesChanged(unsigned int, unsigned int, AudioObjectPropertyAddress const*) 8 CoreAudio HALC_ProxyNotifications::CallListener(unsigned int, unsigned int, unsigned int, AudioObjectPropertyAddress const*) In v0.41.0, audio/out/ao_coreaudio.c hotplug_cb() calls MP_VERBOSE(ao, "Handling potential hotplug event...") as its first action. The fault address 0x0 inside mp_msg_va indicates the log context was NULL when the callback executed on CoreAudio's dispatch queue. Since the callback runs outside mpv's own threading/lifecycle control, this looks like a missing null guard or an init/teardown race. The full macOS crash reports of both incidents are attached. ### Log File Full macOS crash reports of both incidents (identical crash signature, ~9.5 hours apart) are attached: [mpv-0.41.0-coreaudio-hotplug-crash-reports.txt](https://github.com/user-attachments/files/30126673/mpv-0.41.0-coreaudio-hotplug-crash-reports.txt) ### Sample Files _No response_ ### I carefully read all instruction and confirm that I did the following: - [x] I tested and confirmed that the issue exists with the [latest release version](https://github.com/mpv-player/mpv/releases/latest) or newer. - [x] I provided all required information including system and mpv version. - [x] I produced the log file with the exact same set of files, parameters, and conditions used in "Reproduction Steps", with the addition of `--log-file=output.txt`. - [x] I produced the log file while the behaviors described in "Actual Behavior" were actively observed. - [x] I attached the full, untruncated log file. - [x] I attached the backtrace in the case of a crash.

Please let me know if you need some ffmpeg examples to perform this task.

Hope this helps!

Dom

P.S. I also export to PNG files so I can resume processing without losing anything. I have also written some scripts to monitor progress and perform backups in real-time

david.vaughn · September 16, 2026, 5:53pm

I just updated Topaz Video and before that to macOS Golden Gate 27. Application crashed trying to open twice and then crashed trying to upscale 2-minute video to 4K twice. Crash whether or not on computer or being charged for tokens in Cloud. Solutions?

kyle.topazlabs · September 16, 2026, 5:56pm

Can you send the logs and crash reports to the support team for review into this situation? help@topazlabs.com

To gather logs, please select Help > Logging > Get Logs for Support and attach the zip file to your reply.

Here is a video to help with the steps of how to collect the logs.

konrad.ciecierski · September 16, 2026, 6:03pm

Yes, I can confirm it is this issue. When the input file has no audio all works fine.
Curious, that before the Golden Gate problem did not manifest.

Well it is a bug then and as Topaz it is not a free software, I am awaiting a fix.

robd003 · September 17, 2026, 8:46pm

I just tried Topaz Video 1.7.0 as a demo on my M5 Max and it crashed as the video was finishing.

I’d like to buy Topaz Video, but I’m waiting until it actually works on macOS 27.

konrad.ciecierski · September 18, 2026, 5:53am

By the way, on Jul 29 I have submitted to Topaz another bug. When upscaling some files with rhea on Windows the process of upscaling fails just at the start. On Jul 30 I have got a reply from helpdesk to apply a workaround, to not use the automatic advanced tuning, but select a manual one and then click the ‘estimate’ button. It is ok with couple of files, but it is not a solution when 100+ files need to be processed.

The helpdesk wrote ‘I’ve passed this info along to our team and also created a bug report for Rhea on auto for our team to look into fixing!’… over two months have passed and the bug has not been fixed.

Ren · September 18, 2026, 6:01pm

The new Mac Studios will start arriving next week with MacOS 27 installed. They need to have it working soon.

Ren · September 25, 2026, 6:22pm

I have been trying Topaz version 1.7.1 with OS 27. Constantly crashes while using Starlight precise or Starlight Mini. The only way I have been able to get an extended run is to disable the energy saving setting that turns off the monitor. I also have to leave the topaz app running on the screen rather than minimizing it to the bottom bar.

domdom · September 25, 2026, 6:27pm

Can you try removing the audio stream from your video? I have been experiencing this for months and found this was effective.