I have also replicated this crash on Linux Mint 18.3, just to provide another datapoint. I haven't got around to learning fusion yet but found resolve to be pretty reliable lately in the other pages.System details below.

I dont use other OS since v15.I chose BMD because it supported linux, which I use for many, many years now. I did some tests with a Hackintosh but I find it slower and not as convenient for me.I'm just hoping now that BMD will do something to fix that. It has allowed us the use sound without external card (Decklink) with the v15, so I trust them

Like davorin, as soon as I create a background node and attempt to render it (by connecting it or puting it on a viewer), Davinci Resolve crashes with the above trace.

It happens only when I choose CUDA. When selecting OpenCL, I do not have this issue, but I get another blocking issue (almost anytime I attempt to play somethings, the GUI Thread get stuck after playing 2-3 frames, and eat 100% of the CPU, and I need to kill it, but it's off topic here, and see the disclaimer below anyway.)

Disclaimer: I'm far from running the required hardware and software: Debian Buster, i7 3770 (non K), 16GB, GTX670 2GB, driver 390.87. I understand that I'm well below the requirements. (I'm in the process of upgrading everything.) However, few days ago, before upgrading my distribution and upgrading Davinci Resolve (15.1 -> 15.2) I was able to fully use it without any glitches (for small tests and some fusion effects, following various tutorials, in 2K and 4K). I think I was using OpenCL at the time (before I got the other issue mentioned above.)

I would be happy to provide more details if necessary, if it make sense given my configuration.

I'm using the Free version of Davinci Resolve 15.2, on a dual monitor setup (2560x1440 + 1920x1080) but also tried by booting with only the 2560x1440 one. I have a P8Z77-V DELUXE motherboard (I doubt it matter, but given that the Linux distribution might not be the issue, I'm trying to imagine which common factor remain).

CPU flags: (I think I enabled the VT-d virtualization option in the BIOS for my CPU, reported as vmx here, which is off by default)

I've given up on BMD support...been now a month since I submitted crash details including backtrace...and they only accepted it since I could prove that the exact crash happens also on CentOS7, famous for their obsolete kernel and packages...

Since then I also didn't touch Resolve Studio just for a quick test with 15.2.

I assume they are occupied with how to implement RTX support after their bold announcement, which I still don't see what it is all about...or even the bolder eGPU product with the old RX570 GPU

Still Resolve is a great video editor, but you don't need the paid version as Fusion is still buggy, and was confirmed by BMD here that it takes until August 2019 to have all sorted out.

Currently I've spent more time with Blender and put some money into Octane as I am into 3d compositing. And with Blender you also get 3d camera tracking for free, whereas with Resolve you need the paid version. Though both are using the open source OpebCV project for it

We just need to keep pushing BMD to take Linux users more serious who don't want to use their selfbaked CentOS distro as we like to use other up to date software as well, which is impossible with CentOS.

And hey, BMD was able to release a Debian version for their MediaExpress software, so why not Resolve?Even the old Fusion 9 installs and runs fine on Debian.

If a software is released as free or for US$ 299 I just don't the need for buying a bloody expensive Supermicro Dual-Xeon machine just to be acknowledged by BMD support....

# Tested with Debian Buster# First make sure that you don't have a /usr/lib64 on your system.# In my case, I had some files in /usr/lib64 that belonged to DaVinci Resolve# that I simply removed (because it was pretty obvious that the file didn't matter).# Not sure if it was from an older installation, or simply the current installer# adding files here.ln -s /usr/lib/x86_64-linux-gnu /usr/lib64

Surprisingly it's all that's needed to make the background node works in Fusion... Crazy.

I'm happy. If it stays stable, I will buy the Studio version

I'd like to know if other people who had crashes with the background node in Fusion when using CUDA as the engine, got it working too with this fix.

Another way to fix it, but only if the symlink is not possible (because it would clash with another package for instance), is to run Resolve with something like the following command:

Hi, I may be experiencing a bug related to this but the proposed solution didn't help me.

So, here is my bug report.I ran into an issue whenever I use anything related to Fusion in DaVinci Resolve 15.2.2 that I've installed using makeresolvedeb 15.2.2-1 on Ubuntu 18.10 with kernel 4.20 and AMD ROCm driver. The same happens with amdgpu-pro. The same happens on different kernels and the same happens on Ubuntu 16.04, Ubuntu 18.04 and Ubuntu 18.10.

Whenever I put any Fusion title or use any Fusion effect on the timeline in the edit pane Resolve crashes. I don't get any preview of the title or effect, the prerendering bar above it is red and it does not turn blue at all nor it renders the effect, that part stays black in the preview.

Steps to reproduce: 1. Launch DaVinci Resolve 2. Create new "Untitled Project" 3. Drag any Fusion title on the timeline like Text+ 4. Position the timeline cursor anywhere before the title effect 5. Click play preview button 6. When the timeline cursor gets to the fusion title Resolve should crash, if not repeat step 4. and 5. a few times and it should crash but in any case, the title should not be visible or rendered in the preview as in my case

# Tested with Debian Buster# First make sure that you don't have a /usr/lib64 on your system.# In my case, I had some files in /usr/lib64 that belonged to DaVinci Resolve# that I simply removed (because it was pretty obvious that the file didn't matter).# Not sure if it was from an older installation, or simply the current installer# adding files here.ln -s /usr/lib/x86_64-linux-gnu /usr/lib64

# Tested with Debian Buster# First make sure that you don't have a /usr/lib64 on your system.# In my case, I had some files in /usr/lib64 that belonged to DaVinci Resolve# that I simply removed (because it was pretty obvious that the file didn't matter).# Not sure if it was from an older installation, or simply the current installer# adding files here.ln -s /usr/lib/x86_64-linux-gnu /usr/lib64

Surprisingly it's all that's needed to make the background node works in Fusion... Crazy.

I'm happy. If it stays stable, I will buy the Studio version

I'd like to know if other people who had crashes with the background node in Fusion when using CUDA as the engine, got it working too with this fix.

Another way to fix it, but only if the symlink is not possible (because it would clash with another package for instance), is to run Resolve with something like the following command: