Project Crashes with V 18.1.3 - different reports

Hi,

I am having heavy issues opening two projects with V 18.1.3. DaVinci crashes immediately after opening. MBP 16" M1 16GB Monterey.
No idea, what I might change. Other projects do open.


Project 1 error message (shortened to 1 line):
Kernel Triage: VM - pmap_enter failed with resource shortage

project 2 error message (shortened to fit this forum):

-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Process: Resolve [1715]
Path: /Applications/DaVinci Resolve.app/Contents/MacOS/Resolve
Identifier: com.blackmagic-design.DaVinciResolveLite
Version: 18.1.3 (18.1.30008)
App Item ID: 571213070
App External ID: 854748079
Code Type: ARM-64 (Native)
Parent Process: launchd [1]
User ID: 501

Date/Time: 2023-02-07 13:05:33.0991 +0100
OS Version: macOS 12.6.1 (21G217)
Report Version: 12
Anonymous UUID: 474C83D8-7B6F-3071-3584-A62663B2995A

Sleep/Wake UUID: 3B5825CD-E324-495D-A1A3-A7887A975A5A

Time Awake Since Boot: 10000 seconds
Time Since Wake: 498 seconds

System Integrity Protection: enabled

Crashed Thread: 84

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Thread 0:: GUI Thread Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x19897a8b0 mach_msg_trap + 8
1 libsystem_kernel.dylib 0x19897ad20 mach_msg + 76
2 CoreFoundation 0x198a85210 __CFRunLoopServiceMachPort + 372
3 CoreFoundation 0x198a836c0 __CFRunLoopRun + 1180
4 CoreFoundation 0x198a82a84 CFRunLoopRunSpecific + 600
5 HIToolbox 0x1a16c6338 RunCurrentEventLoopInMode + 292
6 HIToolbox 0x1a16c60b4 ReceiveNextEventCommon + 564
7 HIToolbox 0x1a16c5e68 _BlockUntilNextEventMatchingListInModeWithFilter + 72
8 AppKit 0x19b5ea51c _DPSNextEvent + 860
9 AppKit 0x19b5e8e14 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1328
10 AppKit 0x19b5dafe0 -[NSApplication run] + 596
11 libqcocoa.dylib 0x124590f94 0x124558000 + 233364
12 libQt5Core.5.dylib 0x121729168 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 524
13 libQt5Core.5.dylib 0x12172d634 QCoreApplication::exec() + 132
14 Resolve 0x10384af88 0x1007b0000 + 50966408
15 Resolve 0x103848c68 0x1007b0000 + 50957416
16 Resolve 0x10382028c 0x1007b0000 + 50791052
17 dyld 0x1197c108c start + 520

Thread 1:
0 libsystem_kernel.dylib 0x19897a8ec semaphore_wait_trap + 8
1 Resolve 0x1008649a0 0x1007b0000 + 739744
2 Resolve 0x1007cc29c 0x1007b0000 + 115356
3 libsystem_pthread.dylib 0x1989b826c _pthread_start + 148
4 libsystem_pthread.dylib 0x1989b308c thread_start + 8

Thread 2:: ThreadDispatcher
0 libsystem_kernel.dylib 0x19897e270 __psynch_cvwait + 8
1 libsystem_pthread.dylib 0x1989b883c _pthread_cond_wait + 1236
2 fusionscript.so 0x11adfa300 Fusion::Platform::WaitEvent(Fusion::Platform::_Event*, unsigned int) + 268
3 libfusionsystem.dylib 0x140e60b04 Fusion::ThreadDispatcher::ThreadMain() + 192
4 fusionscript.so 0x11ae0227c 0x11ad74000 + 582268
5 libsystem_pthread.dylib 0x1989b826c _pthread_start + 148
6 libsystem_pthread.dylib 0x1989b308c thread_start + 8

Thread 3:: ThreadDispatcher
0 libsystem_kernel.dylib 0x19897e270 __psynch_cvwait + 8
1 libsystem_pthread.dylib 0x1989b883c _pthread_cond_wait + 1236
2 fusionscript.so 0x11adfa300 Fusion::Platform::WaitEvent(Fusion::Platform::_Event*, unsigned int) + 268
3 libfusionsystem.dylib 0x140e60b04 Fusion::ThreadDispatcher::ThreadMain() + 192
4 fusionscript.so 0x11ae0227c 0x11ad74000 + 582268
5 libsystem_pthread.dylib 0x1989b826c _pthread_start + 148
6 libsystem_pthread.dylib 0x1989b308c thread_start + 8

Thread 4:: ThreadDispatcher
0 libsystem_kernel.dylib 0x19897e270 __psynch_cvwait + 8
1 libsystem_pthread.dylib 0x1989b883c _pthread_cond_wait + 1236
2 fusionscript.so 0x11adfa300 Fusion::Platform::WaitEvent(Fusion::Platform::_Event*, unsigned int) + 268
3 libfusionsystem.dylib 0x140e60b04 Fusion::ThreadDispatcher::ThreadMain() + 192
4 fusionscript.so 0x11ae0227c 0x11ad74000 + 582268
5 libsystem_pthread.dylib 0x1989b826c _pthread_start + 148
6 libsystem_pthread.dylib 0x1989b308c thread_start + 8

[...]

Thread 84 crashed with ARM Thread State (64-bit):
x0: 0x0000000000000000 x1: 0x0000000000000000 x2: 0x0000000000000000 x3: 0x0000000000000000
x4: 0x0000000000000000 x5: 0x0000000000989680 x6: 0x0000000000000000 x7: 0x0000000000000001
x8: 0x7d1774b186ef1b7a x9: 0x7d1774b3251a6b7a x10: 0x00000000000003e8 x11: 0x000000000000000a
x12: 0x0000000000000000 x13: 0x0000000000000033 x14: 0x0000020000010d0a x15: 0x00000001f1415450
x16: 0x0000000000000148 x17: 0x00000001f2adb680 x18: 0x0000000000000000 x19: 0x0000000000000006
x20: 0x00000002a3f57000 x21: 0x0000000000029f07 x22: 0x00000002a3f570e0 x23: 0xffffffffffffffff
x24: 0x00000001eebc2000 x25: 0x00000001eeda2000 x26: 0x00000001a13cdc49 x27: 0x0000600002567b80
x28: 0x000060007525da20 fp: 0x00000002a3f53a60 lr: 0x00000001989b7ee0
sp: 0x00000002a3f53a40 pc: 0x0000000198982d98 cpsr: 0x40001000
far: 0x000000011dacc000 esr: 0x56000080 Address size fault

Give the FAQ a good read. It goes over some troubleshooting steps, as well as what information to post if those fail.

viewtopic.php?f=21&t=90190

Opening Project on Davinci Cloud and immediately crashes when loading the stills.

Running Mac Studio 2022 MacOS Monterrey Apple M1 Max with 64gb memory.

Different computer does not seem to have the same issue opening the project.

MAN!!!! I kept having version 18.1.3 crash on me EVERYTIME in the middle of a project and I kept pulling hairs out!!!!
Searched for the issue online and found ONLY this post about the issue so i reverted back to 18.1.2 from the software support downloads and never had the crash.
So revert back to the previous build and complete your project then wait for Version 1.4

[Peter Chamberlain]

Christian, the log info u posted isn’t helping.

We will only look at the complete resolve generated logs and a windows NFO as per the FAQS

Hi,

I tried following the FAQ.

1. "Diagnostic Log Failed - The log file could not be created, please try again"
There's now a ZIP on my desktop with 1x audiobusingmode.conf and 3x *.plst

2. I searched for Library/ApplicationSupport/Blackmagic it's not there.
I searched within system files and I found the files. But they are in a very weird folder called user/Library/Containers/DaVinci Resolve/

Never saw this container structure before. Monterey might have a problem. Thing is, this M1 16" is brand new when I installed DaVinci fresh.

Will post a Diagnostic Log if that problem is solved before. Any advise welcome.

Hi everyone.

I consulted a colleague of mine who's on Ventura and also a Mac-User forum about that Container issue.

It seems this is a new behavior on a Mac.

I found the *.log-data here, completely new path!
USER/Library/Containers/DaVinciResolve/Data/Library/Application Support/Blackmagic Design/DaVinci Resolve/logs

Please would you like to re-check, if your path in your FAQ's is still valid?
"Mac OS:
In Finder, select "Go to Folder..." (⇧⌘G by default), type the path /Library/Application Support/Blackmagic Design/DaVinci Resolve/ and hit Enter. Run the CaptureLogs application."


Here is a WeTransfer-Link to the log-file:
https://wetransfer.com/downloads/e0d7f2 ... 734/3e26e0

It seems this is a new behavior on a Mac.

For what it's worth, Christian, the logs on my M1 / Ventura laptop are still in the same place as always (~/Library/Application Support/Blackmagic Design/DaVinci Resolve).

Hi Andy,

I made screenshots for you. The Log-files moved. The whole structure seems weird and I would expect this as far as I know if I had downloaded DaVinci on your website and not via App Store.

Screenshot 1: System-Library (empty)
Screenshot 2: User-Library (empty)
Screenshot 3: User/ Library/ Containers/ DaVinci Resolve/ Data/ Library/ Application Support/ Blackmagic Design/ DaVinci Resolve/ logs (yes)

macOS Monterey 12.6.1
What do you think? What went wrong here? I found several users in Mac forum writing the same folder structure via these "containers".

[Dwaine Maggart]

@Christian: You wrote:

Please would you like to re-check, if your path in your FAQ's is still valid?
"Mac OS:
In Finder, select "Go to Folder..." (⇧⌘G by default), type the path /Library/Application Support/Blackmagic Design/DaVinci Resolve/ and hit Enter. Run the CaptureLogs application."

That path is absolutely correct to locate the CaptureLogs.app application. Which is what we want you to run to generate a proper diagnostics log to send to us. We don't want you to go to the actual logs folder and send us stuff from there.