AndyL
5th June 2021, 13:30
I'm having a real problem trying to run QTGMC at the moment - it used to work, but seemed to break after I installed OSX 11.4 (reverting to 11.3.1 has not fixed it)
Main crash log message:
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00007f9750000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [6657]
The crashed thread (almost) always looks something like this:
Thread 20 Crashed:
0 libmvtools.dylib 0x000000010f1db2b9 HorizontalWiener_avx2(unsigned char*, unsigned char const*, long, long, long, long) + 313
1 libmvtools.dylib 0x000000010ef54309 mvpRefine + 505
2 libmvtools.dylib 0x000000010ef645fb mvgofRefine + 43
3 libmvtools.dylib 0x000000010ef68066 mvsuperGetFrame + 870
4 libvapoursynth.dylib 0x000000010e3e8275 VSNode::getFrameInternal(int, int, VSFrameContext&) + 69
5 libvapoursynth.dylib 0x000000010e400fa2 VSThreadPool::runTasks(VSThreadPool*, std::__1::atomic<bool>&) + 2178
6 libvapoursynth.dylib 0x000000010e402fc0 void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (*)(VSThreadPool*, std::__1::atomic<bool>&), VSThreadPool*, std::__1::reference_wrapper<std::__1::atomic<bool> > > >(void*) + 48
7 libsystem_pthread.dylib 0x00007fff204d98fc _pthread_start + 224
8 libsystem_pthread.dylib 0x00007fff204d5443 thread_start + 15
The crash seems to be pretty random - one time it might get several thousand frames in, another it might not reach frame 100.
I've tried a lot of permutations of QTGMC params, and after looking at the crash log, I've tried four different versions of mvtools (versions 20 through 23) v22 seems to crash the least, but it still crashes a good deal.
At my wits end with this one - has anyone come across this, or got any suggestions on how I might be able to deal with it?
Full Crash log attached.
Main crash log message:
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00007f9750000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [6657]
The crashed thread (almost) always looks something like this:
Thread 20 Crashed:
0 libmvtools.dylib 0x000000010f1db2b9 HorizontalWiener_avx2(unsigned char*, unsigned char const*, long, long, long, long) + 313
1 libmvtools.dylib 0x000000010ef54309 mvpRefine + 505
2 libmvtools.dylib 0x000000010ef645fb mvgofRefine + 43
3 libmvtools.dylib 0x000000010ef68066 mvsuperGetFrame + 870
4 libvapoursynth.dylib 0x000000010e3e8275 VSNode::getFrameInternal(int, int, VSFrameContext&) + 69
5 libvapoursynth.dylib 0x000000010e400fa2 VSThreadPool::runTasks(VSThreadPool*, std::__1::atomic<bool>&) + 2178
6 libvapoursynth.dylib 0x000000010e402fc0 void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (*)(VSThreadPool*, std::__1::atomic<bool>&), VSThreadPool*, std::__1::reference_wrapper<std::__1::atomic<bool> > > >(void*) + 48
7 libsystem_pthread.dylib 0x00007fff204d98fc _pthread_start + 224
8 libsystem_pthread.dylib 0x00007fff204d5443 thread_start + 15
The crash seems to be pretty random - one time it might get several thousand frames in, another it might not reach frame 100.
I've tried a lot of permutations of QTGMC params, and after looking at the crash log, I've tried four different versions of mvtools (versions 20 through 23) v22 seems to crash the least, but it still crashes a good deal.
At my wits end with this one - has anyone come across this, or got any suggestions on how I might be able to deal with it?
Full Crash log attached.