In color tab, selecting Color > Auto Color causes a hang of about 20 seconds and then a crash. Using Win10 build 17134. Core i5-6400 @ 2.70, 24 GB ram, dell XPS 8910. Tried it twice and same thing both times. Editing about 30 minutes of GoPro 4k/60fps, so my system is already bogged down quite a bit. Not sure if that's the issue or some other bug.
Hi am experiencing the same issue on a laptop. Model:15-BA061DX
(to be clear, Resolve 15 works fine. And I don't believe it's the driver as others experienced the same exact issue, and I have the newest driver for my system, but of course I don't want to make any assumptions. I am just concerned the answer will be that it is the GPU, when it appears to be a bug issue.)
the autocolor in v16 uses AI, so more machine resources called for, it does work well on my workstations, but they have a wack more resources for the software to tap
Happens frequently on windows 10, resolve 16 lite. Notice that If "auto color" worked once (with some delay as mentioned), it just works fine without a delay for the rest of the editing session. At times resolve just crashes when trying to use the tool for the first time. On linux with resolve 16 lite the "auto color" just not working for me, constant crashes.
My setup: ryzen 7 1700, 4gb ram (plenty of swap on ssd, will upgrade soon i hope) and nvidia 1060 6gb
DaVinci-Resolve-logs-20190917_214409 is Resolve 16.0 windows 10 64 bit DaVinci-Resolve-logs-20190917_221741 is Resolve 16.1b3 windows 10 64 bit (i also have dump file, let me know if you want to look at it) linux_resolve16.1b2 are linux logs All 3 files are just after Resolve crashed. On linux this happens just after "auto color" button is pressed On windows is more tricky to get this option to affect stability
Resolve lite 16.1b3 seems to be unaffected by this on linux. I also tested v16.0 on linux and it's also fine
Charles Bennett wrote:Boris, I see that you only have 4gb RAM. The minimum recommended is 16gb.
Yes, this could be an issue. I will add some memory soon. Anyway i also had this same issue on machine with 16gb of RAM, just don't have logs now and can't even remember the version used. I am using swap on ssd now, also when using "Auto color", heavy grading wasn't used. So there could be something else (I'm not alone with this problem)