-
-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash when Tick policy is set to score-accurate #786
Comments
Still an issue in 2.0.0-a13. Crash report: Process: score [30580] Date/Time: 2018-09-04 16:07:18.740 +0200 Sleep/Wake UUID: 3ACB4F0E-8148-4E85-93EE-57C84FD4E50D Time Awake Since Boot: 190000 seconds System Integrity Protection: enabled Crashed Thread: 16 com.apple.audio.IOThread.client Exception Type: EXC_BAD_ACCESS (SIGSEGV) VM Regions Near 0x18: Thread 0:: Dispatch queue: com.apple.main-thread Thread 1: Thread 2:: Dispatch queue: com.apple.libdispatch-manager Thread 3: Thread 4: Thread 5: Thread 6: Thread 7: Thread 8: Thread 9: Thread 10: Thread 11:: com.apple.NSEventThread Thread 12:: Qt bearer thread Thread 13: Thread 14: Thread 15:: com.apple.audio.IOThread.client Thread 16 Crashed:: com.apple.audio.IOThread.client Thread 16 crashed with X86 Thread State (64-bit): Logical CPU: 2 Binary Images: External Modification Summary: VM Region Summary:
REGION TYPE SIZE COUNT (non-coalesced) Model: MacBookPro11,3, BootROM MBP112.0138.B40, 4 processors, Intel Core i7, 2.5 GHz, 16 GB, SMC 2.19f12 |
When Tick policy (under Preferences -> Execution) is set to score-accurate and playback is started, Score crashes immediately. Tested on OS X 10.11.6 with Score 2.0.0-a4.
The text was updated successfully, but these errors were encountered: