System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: Intel(R) UHD Graphics 600 Intel 4.5.0 - Build 27.20.100.8476
Blender Version
Broken: version: 2.91.0 Alpha, branch: Latest Master, commit date: 06/09 2020
Short description of error
Having Blender running, and after closing the laptop lid, having it hibernating and reopening it the sequencer drawing behaves like this(sequencer area is not redrawn properly, sometimes the panels also goes rainbow colored):
Problem with rainbow panels may be unrelated, but I am not sure if that is the case for 100%.
Does this happen with 2.90?
Try rebuilding. I was experiencing the rainbow panels upon open Blender with various master builds over the last two days. There were additional changes made 2 hours after you created this report. The issue still showed up upon rebuilding for me, but went away after opening and closing Blender a couple of times. My guess is that the opening and closing causes the previous shader cache to clear.
It is still happening. Here's a build of the latest master(only with Richard's Transfrom patch(unrelated to the bug) applied):
A build including that patch, still have that bug:
Are you unable to reproduce it?
I am not able to reproduce.
I have looked at commits from few days before this report, I am not sure how often you compile though.
Possible suspects are
rBd6d2897ef04a7c1b3d5fb357629e534055629857
rBab95cdaba970a30127d804bd1e66ad25ab021ec1
rBbac4606937514405641659d91a30bf3e6832cdf7
Can you do bisect (lot of compiling see end of page https://wiki.blender.org/wiki/Process/Bug_Reports/Triaging_Playbook#Valid_Bug_Reports) or checkout one commit before one of these listed, build and check if there is bug?
@Clément Foucault (fclem) do you know what could caused this?
I'm sorry, but making full builds on my computer is far too slow to do the bisecting. Doing 10 full builds would take me 15-20 hours.
Does this happen with the normal timeline?
What if you hide the preview area?
What if you delete all the strips one by one?
Also please attach the result of running the blender with the blender_debug_gpu.cmd and blender_debug_gpu_glitchworkaround.cmd.
Also please attach the system-info.txt
Do none of you see this after waking up the computer after it's been sleeping(while Blender is running with some video in the sequencer and preview)?
What if you use Sequencer/Preview mode?
(My time is limited)
@Peter Fog (tintwotin), such things are heavily GPU+driver specific. Can't say for everyone, but doesn't happen on my laptop, but its Linux and older GPU.
Bug fixing is a collaboration where reported works together with the developers to nail down root cause of the bug, and developers then fix the code. Please follow troubleshooting steps from Clement. They wouldn't take much time.
@Peter Fog (tintwotin) any update here? I got hold of some intel machine (HD graphics 500) and I haven't seen this problem in latest 2.92 build.
I see this report is "stuck" it seems.
Not saying that this is not an issue anymore (maybe it is), but we would have to hear back from @Peter Fog (tintwotin) .
I will close for now (but we can always repopen if we get additional information).
I stopped using hypernate on that computer, now the computer is gone, and I got a new computer.
Now this happened on my new computer too with 2.93 with a build of the latest master:
Have Blender running, shut down laptop lid to hibernate and reopen.
@Philipp Oeser (lichtwerk) Can you open this bug again?
I have a laptop with a GPU from Intel but I can't replicate the problem.
However, I am not sure what steps to reproduce the problem.
My steps:
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: Intel(R) UHD Graphics 620 Intel 4.5.0 - Build 27.20.100.7988
Blender Version: 3.0.0 Alpha, branch: master, commit date: 2021-04-19 10:20, hash: rBeb06ccc32462
As I do not have anymore time or motivation for a continued investment in the Blender project, I'm giving up on this report for now.
