Resolve disappears if left unused

This has happened throughout the v17 betas, and is still happening at 17b8

Resolve is fine while I'm using it but if I leave it for 15 minutes or so then the app has disappeared when I get back (it doesn't appear in the tasklist).

Logs attached but key info which might be relevant include:

Resolve Studio 17 beta 8
Ryzen 5 3600
32GB RAM
GTX970
Windows 10 20H2 19042.789
Speed Editor connected via bluetooth

I haven't seen that yet.

I don't have a Speed Editor. I wonder if that's relevant.

Similar issue, but mine goes "not responding" rather than vanishing. Resolve 16 did it as well. I'm currently on Windows 10 on a laptop, no special hardware, Resolve 17.0.0.18 (17b6)

Update: When Resolve has previously gone "not responding", it has probably always been left on the Edit page. Today, I left it in the background on the Color page for around an hour, and it was still alive when I went back to it. Also now on Resolve 17.0.0.27 (17b8), but this hasn't changed the "not responding" behaviour when left on the Edit page.

I haven't seen that yet.

I don't have a Speed Editor. I wonder if that's relevant.

Yeah - I read through the logs and there's some BT (Bluetooth?) messages, so I was wondering that.

[Dwaine Maggart]

The BtCommon messages in the log are not Bluetooth related.

I see 2 times in your logs where this happened. On Feb 1 and Feb 3.

On Feb 1, Resolve went to sleep at 17:11, then something brought it out of sleep mode at 17:43 then it went back to sleep at 18:06. Then nothing else in the log.

On Feb 3, Resolve went to sleep at 17:30, then something woke it up at 17:39, then back to sleep at 18:00. Then nothing else in the log.

It may be a coincidence, but those times are pretty close together. Was some other app doing something on the system around 18:00?

I would suggest you set up your computer to not hibernate or sleep. A lot of programs like Resolve have background processes that will not automatically restart on waking up hence the problems. Also, in Windows, USB hubs need to be set to not switch off if they think they see no activity.

The BtCommon messages in the log are not Bluetooth related.

I see 2 times in your logs where this happened. On Feb 1 and Feb 3.

On Feb 1, Resolve went to sleep at 17:11, then something brought it out of sleep mode at 17:43 then it went back to sleep at 18:06. Then nothing else in the log.

On Feb 3, Resolve went to sleep at 17:30, then something woke it up at 17:39, then back to sleep at 18:00. Then nothing else in the log.

It may be a coincidence, but those times are pretty close together. Was some other app doing something on the system around 18:00?

These are just the times when I finish work and think "hmm... I wonder if Resolve is still crashing..." so it's just when I try it.

To be clear (and with thanks to Charles's suggestions) the computer is not set to sleep or hibernate. It's a desktop and that functionality annoys me on desktops so I always disable it.

Dwaine - when you say "Resolve went to sleep" and then "something woke it up" - can you be more specific about what can cause these events?

Thanks for the note re "BTCommon" - is there anything else that might interact with the keyboard that could cause this behaviour?

Also - you got me thinking about device power management, but none of the bluetooth devices (which are just the generic BT hub and the speed editor) have the "Power" tab that allows them to sleep or wake the PC

bluetooth.png (5.64 KiB) Viewed 1330 times

Here's an updated log dump from today. I ran it during the day and it crashed / disappeared as expected, outside the ~18:00 timeframe that I normally run it.

I noticed a bunch of pnlsocket errors in this log - anything to do with the speed editor, after all?

[Dwaine Maggart]

Yes, that is certainly an unusual amount of panel disconnects.

They are appear to be happening during cue or stepping operations.

What were you doing on the system from 14:16 to 14:38? Were you stepping/jogging/shutting with the Speed Editor? Or any other operation in particular?

It's recommended for Resolve use to have the Windows Power Plan set to High Performance. Can you verify your system has that selected?

Yes, that is certainly an unusual amount of panel disconnects.

They are appear to be happening during cue or stepping operations.

What were you doing on the system from 14:16 to 14:38? Were you stepping/jogging/shutting with the Speed Editor? Or any other operation in particular?

It's recommended for Resolve use to have the Windows Power Plan set to High Performance. Can you verify your system has that selected?

I've just set it to "AMD Ryzen High Performance" - there's also a "High Performance" option which I'll try if no difference on the Ryzen plan.

What I was doing was... nothing! I can use Resolve for hours with the speed editor and have no problems - the crash only happens when I leave it untouched for... 20 minutes or so.

Update: No difference with high performance power plan, nor after updating to 17b9

Left the app running and when I came back it was gone.

[Dwaine Maggart]

I'm a bit confused by the logs.

It looks like you launched Resolve at 23:18 on 2-16, and exited in a minute or less.

Then launched at 23:19 and exited in a minute or less.

Then launched at 23:20 and exited in a minute or less.

Then final launch at 23:20:30, and loaded project SKO 6.

The last time stamped log was at 23:21:05.

Then at some point, unfortunately not time stamped, there are 55 step fwd and step rev commands ranging around frames 97417 and 97441. And these are the last thing in the log.


Can you confirm that you generated this log file by using CaptureLogs, and not with the Resolve Help menu?

Did you actually launch and exit Resolve multiple times in rapid succession as mentioned above? If so, what was the reason for that?

The step fwd and rev log entries would be created by moving the Speed Editor Jog wheel in Jog mode. Did you mess with the Jog wheel before stepping away from the system?

The next time this happens, please run System Information and do a File - Save to create a system info .NFO file. Do that before restarting Resolve. Maybe it will have a clue.

I'm a bit confused by the logs.

It looks like you launched Resolve at 23:18 on 2-16, and exited in a minute or less.

Then launched at 23:19 and exited in a minute or less.

Then launched at 23:20 and exited in a minute or less.

Then final launch at 23:20:30, and loaded project SKO 6.

The last time stamped log was at 23:21:05.

Then at some point, unfortunately not time stamped, there are 55 step fwd and step rev commands ranging around frames 97417 and 97441. And these are the last thing in the log.


Can you confirm that you generated this log file by using CaptureLogs, and not with the Resolve Help menu?

Did you actually launch and exit Resolve multiple times in rapid succession as mentioned above? If so, what was the reason for that?

The step fwd and rev log entries would be created by moving the Speed Editor Jog wheel in Jog mode. Did you mess with the Jog wheel before stepping away from the system?

The next time this happens, please run System Information and do a File - Save to create a system info .NFO file. Do that before restarting Resolve. Maybe it will have a clue.

Sorry - this is a separate (but possibly related?) issue in that after a crash, Resolve won't recognise the speed editor. So I kill it and restart it, then it eventually recognises it.
The jogs are me checking that the editor is definitely running, then I leave it (after which it dies).

And yes - this was CaptureLogs.bat

Here's a systeminfo dump, taken while the app is running...

Bump...