VSE is slow when using big numbers as framerate's base #89219

New Issue

Gerard Taulats Braos · 2021-06-16T22:37:03+02:00

2021-06-16 22:37:03 +02:00

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: Intel(R) HD Graphics 4600 Intel 4.3.0 - Build 20.19.15.5171

Blender Version
Broken: version: 3.0.0 Alpha, branch: master, commit date: 2021-06-15 22:44, hash: 4891da8ae2
Worked: Never (2.78 had an internal base limit, preventing this bug to happen)

Short description of error
While the VSE is on screen, if the framerate's base is set to a big number (say 1000), panning or opening side panels is slow. When using the max number (1000000 or big enough) Blender freezes and even crashes (in more powerful computers may not, but surely it'll be slower).

Exact steps for others to reproduce the error

Open a VSE panel
Set the framerate's base to 1000000 (In Properties/Scene/Dimensions/Frame Rate/Custom)
Blender slows down/freezes/crashes even.

Notes:

It happens as long as a VSE "sequencer" is on screen, not with the "preview".
I suspect it's due to an unoptimized UI

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: Intel(R) HD Graphics 4600 Intel 4.3.0 - Build 20.19.15.5171 **Blender Version** Broken: version: 3.0.0 Alpha, branch: master, commit date: 2021-06-15 22:44, hash: `4891da8ae2` Worked: Never (2.78 had an internal base limit, preventing this bug to happen) **Short description of error** While the VSE is on screen, if the framerate's base is set to a big number (say 1000), panning or opening side panels is slow. When using the max number (1000000 or big enough) Blender freezes and even crashes (in more powerful computers may not, but surely it'll be slower). **Exact steps for others to reproduce the error** - Open a VSE panel - Set the framerate's base to 1000000 (In Properties/Scene/Dimensions/Frame Rate/Custom) - Blender slows down/freezes/crashes even. Notes: - It happens as long as a VSE "sequencer" is on screen, not with the "preview". - I suspect it's due to an unoptimized UI

Gerard Taulats Braos commented

2021-06-16 22:37:03 +02:00

Added subscriber: @Tabra

Pratik Borhade commented

2021-06-17 15:40:11 +02:00

Added subscriber: @PratikPB2123

Pratik Borhade commented

2021-06-17 15:40:11 +02:00

Can confirm the crash.

atio6axx.dll        :0x00007FFD5199ACB0  DrvPresentBuffers
atio6axx.dll        :0x00007FFD5199ACB0  DrvPresentBuffers
atio6axx.dll        :0x00007FFD5199ACB0  DrvPresentBuffers
atio6axx.dll        :0x00007FFD5199ACB0  DrvPresentBuffers
atio6axx.dll        :0x00007FFD5199ACB0  DrvPresentBuffers
atio6axx.dll        :0x00007FFD5199ACB0  DrvPresentBuffers
atio6axx.dll        :0x00007FFD5199ACB0  DrvPresentBuffers
atio6axx.dll        :0x00007FFD5199ACB0  DrvPresentBuffers
atio6axx.dll        :0x00007FFD5199ACB0  DrvPresentBuffers
atio6axx.dll        :0x00007FFD5199ACB0  DrvPresentBuffers
atio6axx.dll        :0x00007FFD5199ACB0  DrvPresentBuffers
atio6axx.dll        :0x00007FFD5199ACB0  DrvPresentBuffers
atio6axx.dll        :0x00007FFD5199ACB0  DrvPresentBuffers
atio6axx.dll        :0x00007FFD5199ACB0  DrvPresentBuffers
atio6axx.dll        :0x00007FFD5199ACB0  DrvPresentBuffers
atio6axx.dll        :0x00007FFD5199ACB0  DrvPresentBuffers
blender.exe         :0x00007FF6A6550200  blender::gpu::GLImmediate::begin C:\Users\Pratik\Desktop\BlenderOSP\blender\source\blender\gpu\opengl\gl_immediate.cc:116
blender.exe         :0x00007FF6A65333C0  immBegin C:\Users\Pratik\Desktop\BlenderOSP\blender\source\blender\gpu\intern\gpu_immediate.cc:223
blender.exe         :0x00007FF6A65319D0  immRectf C:\Users\Pratik\Desktop\BlenderOSP\blender\source\blender\gpu\intern\gpu_immediate_util.c:70
blender.exe         :0x00007FF6A66B1F30  seq_draw_sfra_efra C:\Users\Pratik\Desktop\BlenderOSP\blender\source\blender\editors\space_sequencer\sequencer_draw.c:2101
blender.exe         :0x00007FF6A66B1580  draw_timeline_seq C:\Users\Pratik\Desktop\BlenderOSP\blender\source\blender\editors\space_sequencer\sequencer_draw.c:2441
blender.exe         :0x00007FF6A5A97410  ED_region_do_draw C:\Users\Pratik\Desktop\BlenderOSP\blender\source\blender\editors\screen\area.c:563
blender.exe         :0x00007FF6A5A7D3E0  wm_draw_window_offscreen C:\Users\Pratik\Desktop\BlenderOSP\blender\source\blender\windowmanager\intern\wm_draw.c:725
blender.exe         :0x00007FF6A5A7D230  wm_draw_window C:\Users\Pratik\Desktop\BlenderOSP\blender\source\blender\windowmanager\intern\wm_draw.c:867
blender.exe         :0x00007FF6A5A7CD70  wm_draw_update C:\Users\Pratik\Desktop\BlenderOSP\blender\source\blender\windowmanager\intern\wm_draw.c:1066
blender.exe         :0x00007FF6A5A596A0  WM_main C:\Users\Pratik\Desktop\BlenderOSP\blender\source\blender\windowmanager\intern\wm.c:654
blender.exe         :0x00007FF6A5A54EB0  main C:\Users\Pratik\Desktop\BlenderOSP\blender\source\creator\creator.c:563
blender.exe         :0x00007FF6A66A3088  __scrt_common_main_seh d:\A01\_work\12\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:288
KERNEL32.DLL        :0x00007FFDAC467020  BaseThreadInitThunk
ntdll.dll           :0x00007FFDADFC2630  RtlUserThreadStart

Can confirm the crash. ```atio6axx.dll :0x00007FFD5199ACB0 DrvPresentBuffers atio6axx.dll :0x00007FFD5199ACB0 DrvPresentBuffers atio6axx.dll :0x00007FFD5199ACB0 DrvPresentBuffers atio6axx.dll :0x00007FFD5199ACB0 DrvPresentBuffers atio6axx.dll :0x00007FFD5199ACB0 DrvPresentBuffers atio6axx.dll :0x00007FFD5199ACB0 DrvPresentBuffers atio6axx.dll :0x00007FFD5199ACB0 DrvPresentBuffers atio6axx.dll :0x00007FFD5199ACB0 DrvPresentBuffers atio6axx.dll :0x00007FFD5199ACB0 DrvPresentBuffers atio6axx.dll :0x00007FFD5199ACB0 DrvPresentBuffers atio6axx.dll :0x00007FFD5199ACB0 DrvPresentBuffers atio6axx.dll :0x00007FFD5199ACB0 DrvPresentBuffers atio6axx.dll :0x00007FFD5199ACB0 DrvPresentBuffers atio6axx.dll :0x00007FFD5199ACB0 DrvPresentBuffers atio6axx.dll :0x00007FFD5199ACB0 DrvPresentBuffers atio6axx.dll :0x00007FFD5199ACB0 DrvPresentBuffers atio6axx.dll :0x00007FFD5199ACB0 DrvPresentBuffers blender.exe :0x00007FF6A6550200 blender::gpu::GLImmediate::begin C:\Users\Pratik\Desktop\BlenderOSP\blender\source\blender\gpu\opengl\gl_immediate.cc:116 blender.exe :0x00007FF6A65333C0 immBegin C:\Users\Pratik\Desktop\BlenderOSP\blender\source\blender\gpu\intern\gpu_immediate.cc:223 blender.exe :0x00007FF6A65319D0 immRectf C:\Users\Pratik\Desktop\BlenderOSP\blender\source\blender\gpu\intern\gpu_immediate_util.c:70 blender.exe :0x00007FF6A66B1F30 seq_draw_sfra_efra C:\Users\Pratik\Desktop\BlenderOSP\blender\source\blender\editors\space_sequencer\sequencer_draw.c:2101 blender.exe :0x00007FF6A66B1580 draw_timeline_seq C:\Users\Pratik\Desktop\BlenderOSP\blender\source\blender\editors\space_sequencer\sequencer_draw.c:2441 blender.exe :0x00007FF6A5A97410 ED_region_do_draw C:\Users\Pratik\Desktop\BlenderOSP\blender\source\blender\editors\screen\area.c:563 blender.exe :0x00007FF6A5A7D3E0 wm_draw_window_offscreen C:\Users\Pratik\Desktop\BlenderOSP\blender\source\blender\windowmanager\intern\wm_draw.c:725 blender.exe :0x00007FF6A5A7D230 wm_draw_window C:\Users\Pratik\Desktop\BlenderOSP\blender\source\blender\windowmanager\intern\wm_draw.c:867 blender.exe :0x00007FF6A5A7CD70 wm_draw_update C:\Users\Pratik\Desktop\BlenderOSP\blender\source\blender\windowmanager\intern\wm_draw.c:1066 blender.exe :0x00007FF6A5A596A0 WM_main C:\Users\Pratik\Desktop\BlenderOSP\blender\source\blender\windowmanager\intern\wm.c:654 blender.exe :0x00007FF6A5A54EB0 main C:\Users\Pratik\Desktop\BlenderOSP\blender\source\creator\creator.c:563 blender.exe :0x00007FF6A66A3088 __scrt_common_main_seh d:\A01\_work\12\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:288 KERNEL32.DLL :0x00007FFDAC467020 BaseThreadInitThunk ntdll.dll :0x00007FFDADFC2630 RtlUserThreadStart ```

Pratik Borhade commented

2021-06-17 15:47:36 +02:00

Changed status from 'Needs Triage' to: 'Confirmed'

Pratik Borhade commented

2021-06-17 15:47:36 +02:00

Looks like driver time out occurred when reproducing the bug

Richard Antalik commented

2021-06-21 11:01:26 +02:00

Added subscriber: @iss

Richard Antalik commented

2021-06-21 11:01:26 +02:00

In #89219#1178271, @PratikPB2123 wrote:
Looks like driver time out occurred when reproducing the bug

Not sure if we could blame this on driver, I think issue is that it is trying to draw too many ticks in timeline.

> In #89219#1178271, @PratikPB2123 wrote: > Looks like driver time out occurred when reproducing the bug Not sure if we could blame this on driver, I think issue is that it is trying to draw too many ticks in timeline.

Gerard Taulats Braos commented

2021-08-02 19:04:51 +02:00

Changed status from 'Confirmed' to: 'Resolved'

Gerard Taulats Braos closed this issue

2021-08-02 19:04:51 +02:00

Gerard Taulats Braos commented

2021-08-02 19:07:20 +02:00

I closed it since this issue does not occur anymore. There are other issues with edge cases though, but only affecting UI so I'll open another report.

Richard Antalik commented

2021-08-02 19:34:24 +02:00

Thanks I almost forgot to close this

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

VSE is slow when using big numbers as framerate's base #89219