EDITED POST
Wavelab 9.5.50 (build 208) bug, not on previous version downloaded around september last year) I tested it before updating this morning
- FIRST CONFIGURATION : High Sierra on a Octocore MacPro5,1 with 32GB Ram & ATI Radeon HD 4870
- SECOND CONFIGURATION : Mojave 10.14.5 on 3,5 GHz 6-Core Intel Xeon E5 32Gb Ram (early 2013 cylinder) with AMD FirePro D500 3 Go
This workflow reproduces bug every time
- Create New Batch single or multicore
- Custom plugin chain : instantiate UV22. It defaults to 16 bit, I change it to 24 bit
- Closing the UV22 windows => Wavelab quits suddenly and the mac issues a crash report (BEGINNING PASTED BELOW)
Best regards
Mark Haliday
CUSTOM STUDIO
ON FIRST CONFIGURATION :
Process: WaveLab Pro 9.5 [5304]
Path: /Applications/WaveLab Pro 9.5.app/Contents/MacOS/WaveLab Pro 9.5
Identifier: net.steinberg.WaveLab-Pro-9-5
Version: 9.5.50.208 (9.5.50.208)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: WaveLab Pro 9.5 [5304]
User ID: 501
Date/Time: 2019-06-15 18:09:40.222 +0200
OS Version: Mac OS X 10.13.6 (17G65)
Report Version: 12
Anonymous UUID: 17F4546B-1294-29C4-8A03-2AB8ABD345A2
Sleep/Wake UUID: 1F9D4E2E-344A-4A08-ABB8-137526FE8702
Time Awake Since Boot: 17000 seconds
Time Since Wake: 4000 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000018
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [0]
VM Regions Near 0x18:
→
__TEXT 000000010cd38000-000000010f02f000 [ 35.0M] r-x/rwx SM=COW /Applications/WaveLab Pro 9.5.app/Contents/MacOS/WaveLab Pro 9.5
Application Specific Information:
objc_msgSend() selector name: isKindOfClass:
