I am facing weird issue with python on my MAC system. It is conflicting with Da Vinci resolve. I checked the log. Is there a way to have both softwares on MAC
Please provide details, e.g. how the conflict manifests, what you found in the log, etc.
[quote=“Nils Philippsen, post:2, topic:60650, full:true, username:Nils”]
Please provide details, e.g. how the conflict manifests, what you found in the log, etc.
==========[CRASH DUMP]==========
#TIME Wed Aug 7 12:19:21 2024 - Uptime 00:00:08 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve v18.6.6.0007 (macOS/Clang arm64)
#BMD_ARCHITECTURE arm64
#BMD_BUILD_UUID 1e3a1442-df7c-40d7-92e8-dd8b91b5f384
#BMD_GIT_COMMIT 3f827ef0d730e66d9a676870f5237d1a0008c1ec
#BMD_UTIL_VERSION 18.6.6.0007
#OS macOS
0 Resolve 0x0000000102272178 Resolve + 549240
1 Resolve 0x0000000102271494 Resolve + 545940
2 libsystem_platform.dylib 0x000000018c949a24 _sigtramp + 56
3 Python 0x0000000321d6b840 import_run_extension + 564
4 Python 0x0000000321d6b840 import_run_extension + 564
5 Python 0x0000000321d6b494 create_builtin + 416
6 Python 0x0000000321d6c6c8 _imp_create_builtin + 96
7 Python 0x0000000321bef458 cfunction_vectorcall_O + 104
8 Python 0x0000000321cf7e4c _PyEval_EvalFrameDefault + 57160
9 Python 0x0000000321b68e4c _PyObject_VectorcallTstate + 88
10 Python 0x0000000321b6d9e4 object_vacall + 256
11 Python 0x0000000321b6d86c PyObject_CallMethodObjArgs + 108
12 Python 0x0000000321d69364 PyImport_ImportModuleLevelObject + 3464
13 Python 0x0000000321d05c40 _PyEval_EvalFrameDefault + 113980
14 Python 0x0000000321ce85cc PyEval_EvalCode + 132
15 fusionscript.so 0x000000011f24d828 initfusionscript + 22948
16 fusionscript.so 0x000000011f24facc PyInit_fusionscript + 5664
17 fusionscript.so 0x000000011f2469d0 _ZN6Fusion12FusionScript17Py3ScriptLanguage9_NewStateEPNS_12ScriptObjectEj + 88
18 fusionscript.so 0x000000011f261fd4 _ZN6Fusion12FusionScript14ScriptLanguage8NewStateEPNS_12ScriptObjectEj + 28
19 libfusionsystem.dylib 0x0000000284fbdb08 _ZN6Fusion9LuaScript16ScriptThreadMainEv + 1480
20 fusionscript.so 0x000000011f244a58 _ZN6Fusion8Platform9NewThreadEPFyPvES1_jPy + 416
21 libsystem_pthread.dylib 0x000000018c91b034 _pthread_start + 136
22 libsystem_pthread.dylib 0x000000018c915e3c thread_start + 8
Signal Number = 11
I’m just speculating – DaVinci Resolve is proprietary software and the crash dump tells very little – but it looks as if it crashes deep down in its own code (frames 15-22) because of a segmentation fault (accessing memory from an illegal address). I would say you should take this up with their support.
I have taken up with their support. They told me to install the latest version. But now I have installed and older version and seems to be working fine. If python version are conflicting and solving the issue then my understanding is that it has to be python not the other way around
No, it just shows that that version of DaVinci Resolve and that version of Python don’t work together well – it could be that Resolve uses the API wrongly in a place, or Python doesn’t implement a part of its API as documented, for instance (or something else). There’s not enough information to “assign blame” which is unhelpful anyway. One thing is clear though: Blackmagic Design is in a far better position to debug this issue, because they have access to the source code of Resolve while the rest of the world doesn’t.