Resolve 17.1 Keep Crashing and Corrupting Project

This has occurred twice now in the same way: When copying and pasting clips between projects then Resolve 17.1 crashed and resulted in a corrupt project that will not reload. Restoring the project from a backup drp and then continuing resulted in another crash and corrupt project that won't reload. The projects are 4K scope and the destination project into which I'm pasting footage had two timelines open; one for the main feature and another "sandbox" timeline for messing around being creative. This is costing serious time now (its a feature film...) so I'm making a post. Logs are attached. Wish me luck...

[Dwaine Maggart]

The 2 most recent crashes happened immediately after trying, and failing, to read this wav file:

\\mediaserver01\MediaServer01\The Last Trip Main Film Content RAW files and other projects MASTER FOOTAGE\6 THE LAST TRIP SIX A\Day 68 Audio Meeting Room Flashbacks and Railway Station\03-02-19\FILMABOUTALONGFILM-131.WAV

If you make a new project and add this file to it, does it also crash?

Also open the Windows System Information app, and do a File - Save, to generate a .NFO file, and send that as well.

The 2 most recent crashes happened immediately after trying, and failing, to read this wav file:

\\mediaserver01\MediaServer01\The Last Trip Main Film Content RAW files and other projects MASTER FOOTAGE\6 THE LAST TRIP SIX A\Day 68 Audio Meeting Room Flashbacks and Railway Station\03-02-19\FILMABOUTALONGFILM-131.WAV

If you make a new project and add this file to it, does it also crash?

Also open the Windows System Information app, and do a File - Save, to generate a .NFO file, and send that as well.

The file "FILMABOUTALONGFILM-131.WAV" loads perfectly in a new test project; no crashing. It saves and it reloads. However, the recorded filepath to it is a legacy one; it reflects a supplier's system, not mine.
Win sysinfo (.nfo) file attached (zipped) as requested. It's probably full of DCOM errors - I know about those.

[Dwaine Maggart]

OK, then just a coincidence that the crash happened after those read errors. The read errors makes sense if that's not a valid path.

Please send project export .drp's of a pair of projects that would allow us to attempt to reproduce the issue at our end, along with details of what clips to try to copy to which timeline in the other project.

OK, then just a coincidence that the crash happened after those read errors. The read errors makes sense if that's not a valid path.

Please send project export .drp's of a pair of projects that would allow us to attempt to reproduce the issue at our end, along with details of what clips to try to copy to which timeline in the other project.

Thanks for the update. Unfortunately I'm not at liberty to send projects or any material from these projects - or even empty projects without linked media (and there's 30TB of media). We are under non-disclosure agreements because the material is for an upcoming cinema feature film. Our hands are somewhat tied. It must be frustrating for you when trying to duplicate a problem that's been raised and you get nothing to work with - and its similarly frustrating for us, because we'd REALLY like to help solve the problem.

Copying and pasting between timelines has not been without problems since version 16.x. In version 16.x I would frequently get "GPU memory full" warnings when that plainly wasn't true (12GB Quadro only 60% used). Ver 17.x seems to be more tolerant of GPU memory usage - but will frequently crash without warning (once every 3 hours very rough estimate) and taking the project with it when working dual timelines in long-form projects. The upside is that I'm very good at database restoring now...

I guess I'll have to limit dual / multiple timelines to small projects for now.

Best regards.

[Shrinivas Ramani]

Hi Julian

Can you try the 17.1.1 update released yesterday and let us know if you still see the issue?

Thanks
Shrinivas

Hi Julian

Can you try the 17.1.1 update released yesterday and let us know if you still see the issue?

Thanks
Shrinivas

I'm on 17.1.1 and - so far, excepting one sporadic crash - it seems to be working OK between two timelines in a short-form project (3mins). Not attempted working long-form projects (2 hours+) in this style yet.

17.1.1 has definitely fixed this issue though: viewtopic.php?f=21&t=137274