Regression: Video sequencer screen corruption occurs when resizing #98620

New Issue

Greg Suing · 2022-06-06T02:25:24+02:00

Greg Suing commented

2022-06-06 02:25:24 +02:00

System Information
Operating system: Windows 11
Graphics card: Intel UHD Graphics 770

Blender Version
Broken: 3.2.0 Release Candidate, branch: master, commit date: 2022-06-03 16:56, hash: 34f94a02f3, type: release
Worked: 3.0.x, 3.1.0

Short description of error
Video sequencer screen corruption occurs (random colored lines and rectangles) when resizing sequencer

Bisected to 439f86ac89.

Exact steps for others to reproduce the error

launch Blender 3.2.0 Candidate (the same issue occurs in 3.3.0 alpha)
choose Video Editing
resize sequencer region by moving the splitter above the sequencer (corruption occurs - looks like uninitialized memory)
resize the main application window to see more corruption that looks like uninitialized memory.

#98620.mp4

**System Information** Operating system: Windows 11 Graphics card: Intel UHD Graphics 770 **Blender Version** Broken: 3.2.0 Release Candidate, branch: master, commit date: 2022-06-03 16:56, hash: 34f94a02f370, type: release Worked: 3.0.x, 3.1.0 **Short description of error** Video sequencer screen corruption occurs (random colored lines and rectangles) when resizing sequencer Bisected to 439f86ac89. **Exact steps for others to reproduce the error** 1. launch Blender 3.2.0 Candidate (the same issue occurs in 3.3.0 alpha) 2. choose Video Editing 3. resize sequencer region by moving the splitter above the sequencer (corruption occurs - looks like uninitialized memory) 4. resize the main application window to see more corruption that looks like uninitialized memory. [#98620.mp4](https://archive.blender.org/developer/F13135319/T98620.mp4)

Greg Suing commented

2022-06-06 02:25:24 +02:00

Added subscriber: @gsuing

blender-admin commented

2022-06-06 02:25:24 +02:00

#98934 was marked as duplicate of this issue

Pratik Borhade commented

2022-06-06 06:23:35 +02:00

Added subscriber: @PratikPB2123

Pratik Borhade commented

2022-06-06 06:23:35 +02:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Pratik Borhade commented

2022-06-06 06:23:35 +02:00

Hi, thanks for the report. I managed to reproduce this for once only (occurred right after I open the sequencer tab).
Could you upload screen recording to show us the exact steps?

Blender version: 3.3, 8589f60546b3
Operating system: Windows-10-10.0.19043-SP0 64 Bits
Graphics card: Intel(R) UHD Graphics 620 Intel 4.5.0 - Build 30.0.101.1660```

Hi, thanks for the report. I managed to reproduce this for once only (occurred right after I open the sequencer tab). Could you upload screen recording to show us the exact steps? ```System Information: Blender version: 3.3, 8589f60546b3 Operating system: Windows-10-10.0.19043-SP0 64 Bits Graphics card: Intel(R) UHD Graphics 620 Intel 4.5.0 - Build 30.0.101.1660```

Greg Suing commented

2022-06-06 18:53:09 +02:00

#98620.mp4

[#98620.mp4](https://archive.blender.org/developer/F13135319/T98620.mp4)

Greg Suing commented

2022-06-06 19:53:36 +02:00

The video shows the following steps:

launch Blender 3.2.0 Candidate (the same issue occurs in 3.3.0 alpha)
choose Video Editing
resize sequencer region by moving the splitter above the sequencer (corruption occurs - looks like uninitialized memory)
resize the main application window to see more corruption that looks like uninitialized memory.

The video shows the following steps: 1. launch Blender 3.2.0 Candidate (the same issue occurs in 3.3.0 alpha) 2. choose Video Editing 3. resize sequencer region by moving the splitter above the sequencer (corruption occurs - looks like uninitialized memory) 4. resize the main application window to see more corruption that looks like uninitialized memory.

Pratik Borhade changed title from ~~Video sequencer screen corruption occurs when resizing~~ to Regression: Video sequencer screen corruption occurs when resizing

2022-06-07 14:07:22 +02:00

Pratik Borhade commented

2022-06-07 14:07:26 +02:00

Changed status from 'Needs User Info' to: 'Confirmed'

Pratik Borhade commented

2022-06-07 14:07:26 +02:00

Thanks for the information. I managed to repro this again (but does not occur frequently)
Will mark this as confirmed for now.
Will also ask others if they can repro or not

Thanks for the information. I managed to repro this again (but does not occur frequently) Will mark this as confirmed for now. Will also ask others if they can repro or not ![image.png](https://archive.blender.org/developer/F13136695/image.png)

Omar Emara commented

2022-06-07 14:19:30 +02:00

Added subscriber: @OmarEmaraDev

Omar Emara commented

2022-06-07 14:19:30 +02:00

I can reproduce reliably every time on an older AMD GPU, though can't reproduce with software GL.

Thomas Dinges commented

2022-06-07 15:20:35 +02:00

Added subscriber: @ThomasDinges

Thomas Dinges commented

2022-06-07 15:20:35 +02:00

I cannot reproduce this, tested on all three machines of mine (Windows+AMD, Windows+Intel, Mac+M1). No screen issues here. Tested with latest 3.2 build.

Richard Antalik commented

2022-06-07 15:20:56 +02:00

Added subscriber: @iss

Richard Antalik commented

2022-06-07 15:20:57 +02:00

Can't reproduce here. Since software GL works well, it's most likely issue is within GPU driver.

Not sure if I should lower priority, parhaps there is workaround, if origin of error is identified by bisecting. I assume this is not caused by VSE commit though so changed module tag to viewport.

Can't reproduce here. Since software GL works well, it's most likely issue is within GPU driver. Not sure if I should lower priority, parhaps there is workaround, if origin of error is identified by bisecting. I assume this is not caused by VSE commit though so changed module tag to viewport.

Omar Emara commented

2022-06-07 15:25:11 +02:00

Do you need me to bisect?

Richard Antalik commented

2022-06-07 15:31:28 +02:00

Added subscriber: @fclem

Richard Antalik commented

2022-06-07 15:31:28 +02:00

@OmarEmaraDev If you have time you can bisect. I would ask @fclem if such effort would be helpful though.

Greg Suing commented

2022-06-07 18:37:18 +02:00

I can reliably reproduce this every time. I have a modern processor:

12th Gen Intel(R) Core(TM) i5-12600 3.30 GHz, 32Gb RAM

I can reliably reproduce this every time. I have a modern processor: 12th Gen Intel(R) Core(TM) i5-12600 3.30 GHz, 32Gb RAM

Omar Emara commented

2022-06-08 11:52:44 +02:00

Bisected to 439f86ac89.

Bisected to 439f86ac89.

Jeroen Bakker commented

2022-06-08 12:00:29 +02:00

Added subscriber: @Jeroen-Bakker

Jeroen Bakker self-assigned this 2022-06-08 12:00:29 +02:00

Jeroen Bakker commented

2022-06-08 12:00:29 +02:00

Should be done in master, add windows to the workaround.

blender-admin commented

2022-06-08 13:15:28 +02:00

This issue was referenced by 23bce4a974

This issue was referenced by 23bce4a9749de034608f765c2e91aed19bff55ec

blender-admin commented

2022-06-08 13:15:28 +02:00

This issue was referenced by 7a751327fa

This issue was referenced by 7a751327fab1befb49cec68b82b0d9e98374e1c6

Jeroen Bakker commented

2022-06-08 13:17:22 +02:00

Changed status from 'Confirmed' to: 'Resolved'

Jeroen Bakker closed this issue

2022-06-08 13:17:22 +02:00

Georg K commented

2022-06-08 15:01:14 +02:00

Added subscriber: @georgK

Georg K commented

2022-06-08 15:01:14 +02:00

Sorry for chiming in, but since this is so very similar, I was hoping that my issue could be solved in a similar way: https://developer.blender.org/T86686 (has been closed because nobody could reproduce it, but I see it in 3.2/3.3 every day - probably thanks to my old AMD card and mesa).
before this patch:
after this patch: (did not get worse, it is just different each time)
Sometimes, fractions of images can be recognized that were once on screen (but have been closed hours before starting Blender), so it seems like some buffer is not cleared. The gravity of the issue seems to be affected by the mesa driver version, but it was not present in 3.1.2

Sorry for chiming in, but since this is so very similar, I was hoping that my issue could be solved in a similar way: https://developer.blender.org/T86686 (has been closed because nobody could reproduce it, but I see it in 3.2/3.3 every day - probably thanks to my old AMD card and mesa). before this patch: ![commit date 2022-06-07 07-42, hash 4580c18c56f6.png](https://archive.blender.org/developer/F13138363/commit_date_2022-06-07_07-42__hash_4580c18c56f6.png) after this patch: ![commit date 2022-06-08 11-15, hash 7a751327fa.png](https://archive.blender.org/developer/F13138365/commit_date_2022-06-08_11-15__hash_rB7a751327fab1.png) (did not get worse, it is just different each time) Sometimes, fractions of images can be recognized that were once on screen (but have been closed hours before starting Blender), so it seems like some buffer is not cleared. The gravity of the issue seems to be affected by the mesa driver version, but it was not present in 3.1.2

Omar Emara commented

2022-06-08 15:19:46 +02:00

@georgK I also have the same issue on an older AMD GPU on Mesa, and the same workaround fixes the issue for me if applied on my GPU, so your problem can probably be solved in a similar way.

Greg Suing commented

2022-06-08 18:10:46 +02:00

Yay, this is fixed in the 3.3.0 Master D15134 branch. Thank you. Not seeing it fixed in 3.2.0 Stable yet.

Yay, this is fixed in the 3.3.0 Master [D15134](https://archive.blender.org/developer/D15134) branch. Thank you. Not seeing it fixed in 3.2.0 Stable yet.

Pratik Borhade commented

2022-06-10 06:39:29 +02:00

@Jeroen-Bakker hi, would it be ok to mention this fix for corrective release? #98661 (3.2: Potential candidates for corrective releases)

Cole commented

2022-06-13 08:47:58 +02:00

Added subscriber: @Cole-Marcus

Cole commented

2022-06-13 08:47:58 +02:00

Not seeing it fixed in 3.2.0 Stable yet.

It seems to be fixed for me in 3.2 Stable.

System Information
Blender version: 3.2 release
Operating system: Windows 10 Pro Version 21H2 (OS Build 19044.1741)
Graphics card: Intel(R) HD Graphics 4600  .

> Not seeing it fixed in 3.2.0 Stable yet. It seems to be fixed for me in 3.2 Stable. ``` System Information Blender version: 3.2 release Operating system: Windows 10 Pro Version 21H2 (OS Build 19044.1741) Graphics card: Intel(R) HD Graphics 4600 . ```

Greg Suing commented

2022-06-13 15:46:45 +02:00

Definitely not fixed for me.

version: 3.2.0, branch: master, commit date: 2022-06-08 10:22, hash: e05e1e3691, type: release
build date: 2022-06-08, 11:13:18
platform: 'Windows-10-10.0.22000-SP0'

Definitely not fixed for me. > version: 3.2.0, branch: master, commit date: 2022-06-08 10:22, hash: e05e1e369187, type: release > build date: 2022-06-08, 11:13:18 > platform: 'Windows-10-10.0.22000-SP0' ![blender_3.2.0.png](https://archive.blender.org/developer/F13156348/blender_3.2.0.png)

Pratik Borhade commented

2022-06-17 04:56:55 +02:00

Added subscriber: @Ahal-shameem

Georg K commented

2022-06-19 12:37:26 +02:00

The issue is still present in
version: 3.3.0 Alpha, branch: master, commit date: 2022-06-18 22:14, hash: 575884b827, type: Release
build date: 2022-06-19, 10:09:11
platform: 'Linux-5.17.15-1-MANJARO-x86_64-with-glibc2.35'

So, I bisected and found the same commit to be the cause of the issue as Omar:

439f86ac89 is the first bad commit
commit 439f86ac89
Author: Jeroen Bakker jeroen@blender.org
Date: Tue May 10 08:10:46 2022 +0200

  Fix T97272: Lag when resizing viewports.
  
  Viewports where cleared explicitly due to compatibility reasons with Intel iGPUs.
  This slowed down other platforms as well, this wasn't noticeable on all platforms.
  
  This patch will be more selective when to enable the workaround.
  Currently only for iGPUs on Mac + Linux.

source/blender/gpu/GPU_capabilities.h | 1 +
source/blender/gpu/intern/gpu_capabilities.cc | 5 +++++
source/blender/gpu/intern/gpu_capabilities_private.hh | 1 +
source/blender/gpu/intern/gpu_viewport.c | 13 +++++++++----
source/blender/gpu/opengl/gl_backend.cc | 7 +++++++
5 files changed, 23 insertions(+), 4 deletions(-)

In almost all cases, it is not necessary to resize the viewport to see the issue. After clicking "Video Editing" on the splash screen, the artifacts are immediately visible in the VSE.

The issue is still present in version: 3.3.0 Alpha, branch: master, commit date: 2022-06-18 22:14, hash: 575884b82786, type: Release build date: 2022-06-19, 10:09:11 platform: 'Linux-5.17.15-1-MANJARO-x86_64-with-glibc2.35' So, I bisected and found the same commit to be the cause of the issue as Omar: 439f86ac89bdd649aa9ccfe258c5f80474788449 is the first bad commit commit 439f86ac89bdd649aa9ccfe258c5f80474788449 Author: Jeroen Bakker <jeroen@blender.org> Date: Tue May 10 08:10:46 2022 +0200 ``` Fix T97272: Lag when resizing viewports. Viewports where cleared explicitly due to compatibility reasons with Intel iGPUs. This slowed down other platforms as well, this wasn't noticeable on all platforms. This patch will be more selective when to enable the workaround. Currently only for iGPUs on Mac + Linux. ``` source/blender/gpu/GPU_capabilities.h | 1 + source/blender/gpu/intern/gpu_capabilities.cc | 5 +++++ source/blender/gpu/intern/gpu_capabilities_private.hh | 1 + source/blender/gpu/intern/gpu_viewport.c | 13 +++++++++---- source/blender/gpu/opengl/gl_backend.cc | 7 +++++++ 5 files changed, 23 insertions(+), 4 deletions(-) In almost all cases, it is not necessary to resize the viewport to see the issue. After clicking "Video Editing" on the splash screen, the artifacts are immediately visible in the VSE.

Omar Emara commented

2022-06-20 08:38:12 +02:00

@georgK I reopened your original report, so lets handle that there.

Greg Suing commented

2022-06-23 22:52:33 +02:00

Fixed in 3.2.1 candidate. Great job!

Craig Stone commented

2022-07-07 14:46:42 +02:00

Added subscriber: @nobulart

Craig Stone commented

2022-07-07 14:46:42 +02:00

Version 3.2.1 on Ubuntu 22.04 LTS
Older ATI Radeon 5890

system-info.txt

Screencast from 07-07-2022 14:40:28.webm

Version 3.2.1 on Ubuntu 22.04 LTS Older ATI Radeon 5890 [system-info.txt](https://archive.blender.org/developer/F13265424/system-info.txt) [Screencast from 07-07-2022 14:40:28.webm](https://archive.blender.org/developer/F13265426/Screencast_from_07-07-2022_14_40_28.webm)

OlehMel commented

2022-09-10 18:43:22 +02:00

Added subscriber: @Wlnfr

OlehMel commented

2022-09-10 18:43:22 +02:00

Manjaro Linux

System:
  Kernel: 5.15.60-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.1.1
    parameters: BOOT_IMAGE=/vmlinuz-5.15-x86_64
    root=UUID=f8562208-a99c-43fe-a231-253bae0a6f48 rw quiet
    udev.log_priority=3
  Desktop: KDE Plasma v: 5.24.6 tk: Qt v: 5.15.5 wm: kwin_x11 vt: 1 dm: SDDM
    Distro: Manjaro Linux base: Arch Linux

Xeon X5460 and GTX 650(Nvidia 470 driver), Blender 3.3.0
Same issue as comment above and author of the report
2022-09-10 19-31-33.mkv

Manjaro Linux ``` System: Kernel: 5.15.60-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.1.1 parameters: BOOT_IMAGE=/vmlinuz-5.15-x86_64 root=UUID=f8562208-a99c-43fe-a231-253bae0a6f48 rw quiet udev.log_priority=3 Desktop: KDE Plasma v: 5.24.6 tk: Qt v: 5.15.5 wm: kwin_x11 vt: 1 dm: SDDM Distro: Manjaro Linux base: Arch Linux ``` Xeon X5460 and GTX 650(Nvidia 470 driver), Blender 3.3.0 Same issue as comment above and author of the report [2022-09-10 19-31-33.mkv](https://archive.blender.org/developer/F13477508/2022-09-10_19-31-33.mkv)

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Regression: Video sequencer screen corruption occurs when resizing #98620