Blackmagic Forum

Hey y'all, happy for any help here, working on a real sprint of an edit for something screening on Tuesday. Been in it all day, crashed, and now won't open, and 2 backups are also bad.

I'd like to not lose a very critical chunk of work done between 6pm and 8pm. Other projects open fine, and the 3rd oldest backup does too. It was another random crash from clicking a UI element, and now it gets to 96%, beach balls, and has to be force quit.

I have a file share of the drp and a log from one of many open attempts if anyone from support is available. I've tried everything from read only mode to reinstalls. Thank you!

Post the link and someone can take a look.

Peter Chamberlain wrote:Post the link and someone can take a look.

- (Link removed)

For what it's worth Wes, your project just opened on my laptop without issue.
I reexported it for you ... maybe it shook something loose:
Google Drive Link

Andy Mees wrote:For what it's worth Wes, your project just opened on my laptop without issue.
I reexported it for you ... maybe it shook something loose:
Google Drive Link

Thank you SO MUCH for taking the time to do this, I've downloaded it and will be able to test later. Thank you. I just made up the work last night in the end but this will be helpful for troubleshooting.

I've notice that these crashes>corruptions tend to happen more often with Live Save on. I had turned it off a couple years ago, hasn't happened since, thought I'd try again several versions later, guess it's still there. Disabled again.

I work with Live Save on, Wes, I'm not experiencing crash corruptions (touch wood!). Somethings amiss, but of course that's easy for me to say!

Andy Mees wrote:For what it's worth Wes, your project just opened on my laptop without issue.
I reexported it for you ... maybe it shook something loose:
Google Drive Link

Andy wins the internet today! I'm often impressed by the kindness and generosity of Resolve users on the net.

I hope the o.p. will learn from this to always create and hang on to backups, particularly for mission-critical, tight-deadline projects. Backups can truly save your life in situations like these.

Marc Wielage wrote:I hope the o.p. will learn from this to always create and hang on to backups, particularly for mission-critical, tight-deadline projects. Backups can truly save your life in situations like these.

Might wanna read the original post again. Plenty of backups. Not much use when they're also corrupted multiple levels deep.

(returned here because it's happening again on a different project now and noticed I never saw this.)

Marc Wielage wrote:I hope the o.p. will learn from this to always create and hang on to backups, particularly for mission-critical, tight-deadline projects. Backups can truly save your life in situations like these.

Back as yet another project doing the "quit and never reopen" song and dance, and I'm now eight backups deep, captured every 10 minutes. This was open an hour ago, crashed, won't reopen. That's after successfully working in it, quitting, and reopening this morning before this crash, where I changed nothing. So at what point do all these project backups start saving my life? I get 6-10 hard crashes a day on simple projects, this one is like 2 days old with very little work done past ingest. Many of them result in this project lockout.

Perhaps the file will open without incident on another person’s machine as happened before.

Wonder what’s different about your setup that’s causing this?

Man it might be. That’s the thing, I’ve been experiencing this since somewhere in version 18, across both NFS and SMB mounts, as well as internally stored media as a test, but my system otherwise hasn’t changed since this started.

I noticed on the last couple 18 updates & the first few of 19, it seemed like it was prone to crashing for the slightest stuff like clicking a different timeline or opening the inspector.

This project fully saved and closed as normal, and then reopened this morning just to play part of it back, and switching tabs, it crashed. I hadn’t done anything in it during the few-minute session, nothing changed, and now it won’t open.

Have you uploaded a Resolve log and system info file? The log at least should show people at BMD - mostly Dwaine - what Resolve was doing before the crash - and hopefully the stack trace of the crashing thread. The nfo file will show your machine’s config including installed apps and plugins.

Joe Shapiro wrote:Have you uploaded a Resolve log and system info file? The log at least should show people at BMD what Resolve was doing before the crash - and hopefully the stack trace of the crashing thread. The nfo file will show your machine’s config including installed apps and plugins.

It happened previously (before this thread even) and a user said they were able to open the project, sent it back to me, it that worked. IIRC Dwaine or whoever was unable to reproduce it.

Still need to actually fix the problem moving forward, as much as I appreciate their generosity. The insta-corruption is now burning me for the third time on tight-turn work this year alone. Sometimes, one backup is enough, on others, none of them within a reasonable window work (current case). The backup system is kinda pointless if they can't be restored reliably.

They can’t fix it unless they can either reproduce it or learn enough from your logfiles to see what’s going wrong.

I don’t see your logfiles anywhere in this thread. I suggest you attach them as described here:

https://joeshapiro.com/joes-resolve-faq#bug-report

Joe Shapiro wrote:They can’t fix it unless they can either reproduce it or learn enough from your logfiles to see what’s going wrong.

I don’t see your logfiles anywhere in this thread. I suggest you attach them as described here:

https://joeshapiro.com/joes-resolve-faq#bug-report

Correct, this is my problem, they weren't able to reproduce or learn enough from my log files in order to fix the issue. It happens regularly but I guess only to me! haha.

Since making this reply initially today, one of the two projects miraculously started opening, despite me changing nothing, the other one is still borked. There's just no consistency to it. I'm wondering if a fresh database would do it. This was made in 2022 but it's not like they get moldy.

If it were me and loading a project crashed Resolve, I’d either restart Resolve and generate the logs or use the collect logs script to do so. Then I’d attach them here. Just in case this time there’s enough info for them to see what’s crashing.