Is 18.5 just constantly freezing for anyone else?

Usually I can edit on my laptop without any issues, but suddenly today, Resolve is just constantly freezing up my whole computer. Sometimes I can fore quit the program, sometimes I reboot my laptop. Sometimes I can edit for a few minutes before it totally freezes, most of the time it just freezes as soon as I open a project. There's all kinds of other weirdness and glitches that I don't even know how to describe. A lot of weirdness and it's basically unusable for me right now. Just wondering if this is unique to me or if others have had issues since the latest version.

More details as to the system spec may be useful, along with diagnostic logs:
viewtopic.php?f=21&t=90190

More details as to the system spec may be useful, along with diagnostic logs:
viewtopic.php?f=21&t=90190

Thanks! I was just checking first to see if it was a "just me" thing before really diving in to trying to get help figuring it out. There's so much weirdness going on that's hard to explain, and I also thought I'd see if it persisted on my next project. I'll take a look at that linked thread and gather the info.

Yep, happened again today while trying to edit a simple video. After a few minutes the whole computer got really sluggish for a but then just Resolve was extremely sluggish and eventually it just quit. I reopened it and all the video thumbnails had glitched and if I tried to play the videos I got audio but no video (this had happened on the last project as well). I'll attach an image as well as my logs.

Computer info:
Processor AMD Ryzen 5 5500U with Radeon Graphics 2.10 GHz
Installed RAM 12.0 GB (9.85 GB usable)
OS is Windows 11 64 bit, completely up to date.

I do realize that the specs I believe are below the recommended, but the things is, up until a few days ago, I could edit just fine with no issues. I even edited a video with 15 tracks doing split screen. I'm not sure what changed to suddenly cause it to no longer be usable on this machine. As far as I can tell, I think it's fine on my home desktop. I'm away from but actually remoted in to my home machine so I could make a few tweaks to my edit since I couldn't get my laptop to play nicely.

I've also rebooted my laptop MANY times, sometimes so as to quickly get out of the sluggish/frozen state instead of waiting to see if it recovers.

A few more things I've discovered. If I just open a blank project, all seems fine, it didn't appear to freeze. I opened my project in "Read Only" mode and that too seemed fine. Then I opened it again in normal more (not Read Only) and everything immediately froze an remained super sluggish until I could get a program shutdown to eventually register.

I made some changes in "Read Only" mode, then saved it as a copy, and immediate the timeline video thumbnails glitched and showed what looked like video noise and I had no video upon playback. I shut down the program, and reopened the new copy of the project and all was fine. After a few minute of editing everything froze again including my mouse cursor. After a minute or two, everything unfroze, and trying to playback the video in Resolve just showed two flickering alternating frames in the video window while audio played back normally (a behavior that had occurred in the past as well, like I said, a lot of weird behavior that's hard to explain).

[Shrinivas Ramani]

Hi

As you've mentioned, your computer is below minimum specs. One thing you could perhaps try is a clean install of the Adrenaline driver - you can search the forums for the versions that caused problems for other users, and the ones that worked. And consider disabling Windows DCH driver auto updates once you find a stable driver.

Regards
Shrinivas

It seems like there must be some significance that "Read Only" mode doesn't seem to freeze and can still playback and make edits!

Hi

As you've mentioned, your computer is below minimum specs. One thing you could perhaps try is a clean install of the Adrenaline driver - you can search the forums for the versions that caused problems for other users, and the ones that worked. And consider disabling Windows DCH driver auto updates once you find a stable driver.

Regards
Shrinivas

Also I just tried the "Optimize Media" option while in "Read Only" and then saved as a new project which *might* have fixed it. It's hard to tell sometimes since it can take a few minutes for the problem to crop up but so far it's behaving.

I was wrong about the past solutions. They didn't fix it, BUT I may have finally solved it. Time will tell, however after unchecking the box which is nested under Preferences>System>Decode Options>Decode H.264/H.265 using hardware acceleration (which I left checked)>AMD (which I unchecked), I edited for a few minutes as a test without freezing up. Hopefully this luck holds up during my next full edit.

It's constantly freezing or sluggish for me too, was completely fine with the previous version and everything worked smoothly. As far as I know my specs should be fine

i7-10700KF 3.8GHz
32gb RAM
NVIDIA GeForce RTX3080

While Resolve Studio is freezing my CPU, Memory and GPU in the Task Manager are below 30% usage so I've got no idea what the problem is, really regret updating.

[Peter Chamberlain]

Tom, please see the faqs re posting NFO and resolve generated logs

Sound pretty identical to my situation! You might see my last post and see if that solution helps. I haven't tested it super thoroughly but preliminary tests seemed promising!

It's constantly freezing or sluggish for me too, was completely fine with the previous version and everything worked smoothly. As far as I know my specs should be fine

i7-10700KF 3.8GHz
32gb RAM
NVIDIA GeForce RTX3080

While Resolve Studio is freezing my CPU, Memory and GPU in the Task Manager are below 30% usage so I've got no idea what the problem is, really regret updating.

Yep, happened again today while trying to edit a simple video. After a few minutes the whole computer got really sluggish for a but then just Resolve was extremely sluggish and eventually it just quit..

That sounds like you're running out of memory.

Open task manager before Resolve. Watch memory use. You're likely also swapping. A full NVME drive ? Worse a slow HDD.

Do you have anything else open? Chrome ?

Had 18.5 freeze for the first time right after I opened an existing session and grabbed a still. Resolve crashed and was unresponsive. I went to Force Quit, selected Resolve... and it stayed open. I realized, "ah, this is a bigger crash than I thought, and went to Restart the system. Without selecting Restart... the computer basically shut down. I powered it all down, waited a minute, rebooted... and all was fine.

This is on a 2019 Mac Pro running OSX Ventura 13.3. Lost zero work, session was fine. My guess is it momentarily got confused as to how many drives were connected and just choked... but I don't know for sure.

Zero crashes with 18.5 on the laptop or on the Mac Studio Ultra.

Memory and CPU never come close to max. Memory sits around 70%.

Yep, happened again today while trying to edit a simple video. After a few minutes the whole computer got really sluggish for a but then just Resolve was extremely sluggish and eventually it just quit..

That sounds like you're running out of memory.

Open task manager before Resolve. Watch memory use. You're likely also swapping. A full NVME drive ? Worse a slow HDD.

Do you have anything else open? Chrome ?

YES.

On the edge of unusable.

iMac Pro (2017) - All the troubleshooting's been done: no background apps, no CPU hogs, 64GB memory, empty SSD drive, smart render, proxies, pcm audio, prores video, yada yada yada. Long freezes!!! Long waits to even start playing. Some audio tracks get dropped during playback.

I updated my video drivers and things seem to be working again even with the "AMD" box checked under hardware acceleration (mentioned in my earlier reply).

[Shrinivas Ramani]

Heath,
Thanks for the confirmation. There is a sticky thread at the top of this forum about AMD graphics driver issues. Hence my earlier request for a driver update.

Bryn,
Is this the same issue as this post?

Tom,
As Peter says, more detail, and preferably a link to logs would help.

I've linked a post I responded to with a GPU checklist. It would be good to check if there are GPU related complications that contribute to this issue.

Thanks
Shrinivas

Yeah what confused me is that it had worked fine days before and when I looked in my windows update history I didn’t see any video driver updates. I did try to have windows update the driver and it said I already had the most current driver.


So just as a test I downloaded AMD’s drivers instead of just using the windows driver and that may have worked. Time will tell next time I edit.

Heath,
Thanks for the confirmation. There is a sticky thread at the top of this forum about AMD graphics driver issues. Hence my earlier request for a driver update.

Bryn,
Is this the same issue as this post?

Tom,
As Peter says, more detail, and preferably a link to logs would help.

I've linked a post I responded to with a GPU checklist. It would be good to check if there are GPU related complications that contribute to this issue.

Thanks
Shrinivas

No problems on 18.5 on Mac. Completed and distributed 22 minute documentary over 3 weeks without any freezes.

No problems on 18.5 on Mac. Completed and distributed 22 minute documentary over 3 weeks without any freezes.

Yeah, I'm about to start my second feature on 18.5, and it's been "fine so far" (knock on wood).