SantaCruz Posted July 16, 2021 Share Posted July 16, 2021 Affinity Photo 1.9.3 crashed using the Burn tool. Process: Affinity Photo [31497] Path: /Applications/Affinity Photo.app/Contents/MacOS/Affinity Photo Identifier: Affinity Photo Version: 1.9.3 (1.9.237) App Item ID: 824183456 App External ID: 841304071 Code Type: X86-64 (Native) Parent Process: ??? [1] Responsible: Affinity Photo [31497] User ID: 501 Date/Time: 2021-07-16 16:30:50.158 -0700 OS Version: Mac OS X 10.15.7 (19H1217) Report Version: 12 Time Awake Since Boot: 230000 seconds Time Since Wake: 22000 seconds System Integrity Protection: enabled Crashed Thread: 10 Dispatch queue: com.apple.root.default-qos Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x00004546919bbb88 Exception Note: EXC_CORPSE_NOTIFY Termination Signal: Segmentation fault: 11 Termination Reason: Namespace SIGNAL, Code 0xb Terminating Process: exc handler [31497] VM Regions Near 0x4546919bbb88: CoreAnimation 0000000282225000-00000002889d6000 [103.7M] rw-/rwx SM=PRV --> MALLOC_NANO 0000600000000000-0000600008000000 [128.0M] rw-/rwx SM=PRV Thread 10 Crashed:: Dispatch queue: com.apple.root.default-qos 0 liblibpersona.dylib 0x000000011da58d78 DocumentController::AcquireReaderLock() const + 88 1 liblibpersona.dylib 0x000000011981bc99 ViewTile::StaticRender(void*) + 265 2 liblibkernel.dylib 0x0000000111e9e4be invocation function for block in Kernel::Dispatch::DispatchAndForget(std::__1::function<void ()>, Kernel::Dispatch::DispatchPriority) + 46 3 libdispatch.dylib 0x00007fff6dc666c4 _dispatch_call_block_and_release + 12 4 libdispatch.dylib 0x00007fff6dc67658 _dispatch_client_callout + 8 5 libdispatch.dylib 0x00007fff6dc694b0 _dispatch_queue_override_invoke + 763 6 libdispatch.dylib 0x00007fff6dc75957 _dispatch_root_queue_drain + 326 7 libdispatch.dylib 0x00007fff6dc76097 _dispatch_worker_thread2 + 92 8 libsystem_pthread.dylib 0x00007fff6dec19f7 _pthread_wqthread + 220 9 libsystem_pthread.dylib 0x00007fff6dec0b77 start_wqthread + 15 Affinity Photo_2021-07-16-163300_Michaels-iMac.crash Quote Link to comment Share on other sites More sharing options...
Staff Chris B Posted July 19, 2021 Staff Share Posted July 19, 2021 Hey SantaCruz, Is this something you are able to reproduce again at all? I've tried on an older iMac and a new M1 and it seems OK for me. Quote How to format a bug report | Learning Resources | List of V2 FAQs | YouTube Tutorials Link to comment Share on other sites More sharing options...
SantaCruz Posted July 25, 2021 Author Share Posted July 25, 2021 It's a memory allocation crash. Crash occurs in a high pressure memory situation (try using a large file). It doesn't matter how old, or new, your Mac is. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.