Since I have an Ubuntu machine with Postgres, I was curious and just tried it. Indeed, it crashes after creating the DB, and cannot be started on that DB. But if Resolve is started with another DB, the "bad" DB actually works and can be used.
I don't know where such bugs can be reported, so I'll just write the details here, and hopefully BM sees it and can fix it. Since everything seems to work after the initial crash, it might be easy to fix?
My PostgreSQL server is Ubuntu 20.04.4, with PostgreSQL version 12.9.
Resolve is Studio v. 17.4.6 build 4 on Windows 10 20H2.
The database gets created. Nothing appears in the Postgres log which is set to the default "log_min_messages = warning".
The last lines in the Resolve log ("%APPDATA%\Roaming\Blackmagic Design\DaVinci Resolve\Support\logs\ResolveDebug.txt") are
- Code: Select all
[0x00002b4c] | BtCommon | INFO | 2022-04-13 16:42:38,278 | Starting Daemon: C:/Program Files/Blackmagic Design/DaVinci Resolve/DaVinciPanelDaemon.exe
SY panel handler thread starts: 00002660
[0x0000072c] | DbCommon2 | INFO | 2022-04-13 16:42:38,516 | postgres database test_res_ubu_12192.168.81.198 version 12.9 (Ubuntu 12.9-0ubuntu0.20.04.1)
==========[CRASH DUMP]==========
#TIME Wed Apr 13 16:42:38 2022 - Uptime 00:00:03 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve Studio v17.4.6.0004 (Windows/MSVC x86_64)
#BMD_ARCHITECTURE x86_64
#BMD_BUILD_UUID 60c1656b-7224-4553-be5e-126310d247c1
#BMD_GIT_COMMIT 02202f962b16f0d0e861d9284b1b1dcb10a68182
#BMD_UTIL_VERSION 17.4.6.0004
#OS Windows
00007FF739308CEC
00000180A0750324
00007FFCCA2DB86B
0000000000700074
00000000000000A1
0000005F89B1CF90
00007FF739308C40
00007FFCBB8EE6E0
================================
After editing "%APPDATA%\Roaming\Blackmagic Design\DaVinci Resolve\Preferences\
dblist.conf" to let Resolve start with it's normal DB, it does start and shows the new DB.
Then it can be selected, and seems to work fine. I copied a small test project from our normal DB (PG v. 9.6 on CentOS) to the new PG 12.9 on Ubuntu, and could open the project.
However, at the next restart of Resolve with the new DB as default, it crashed again. It also left two ".dmp" files in ...\Support\logs\, one of 3 MB. and another of 467 MB.
The PostgreSQL server log just had:
- Code: Select all
2022-04-13 17:33:59.411 CEST [43937] postgres@test_res_ubu_12 LOG: could not receive data from client: Connection reset by peer