Page MenuHome

Video Sequence Editor Sequencer/Preview Crash
Closed, ResolvedPublicBUG

Description

System Information
Operating system: Windows-10-10.0.18362-SP0 Home 64 bits
CPU: Intel Core i5-3210M @ 2.50 GHz
RAM: 6 GB
Graphics card: GeForce GT 630M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA drivers 391.35 and 369.09
Blender Version
Broken:
Blender 2.83.0, branch: master, commit date: 2020-06-03 14:38, hash: rB211b6c29f771
Blender 2.90.0 Alpha, branch: master, commit date: 2020-06-20 22:15, hash: rBa7f1c68938f9

Worked: Ubuntu 20.04 LTS Linux-5.4.0-37-generic-x86_64-with-debian-bullseye-sid 64 Bits NVIDIA driver 390.132

Short description of error

After resizing a panel in the Sequencer/Preview menu on the Video Sequence Editor and playing the timeline, Blender crashes. The issue seems to not happen on Ubuntu 20.04 LTS, though.

Exact steps for others to reproduce the error

  1. Open either Blender 2.83.0 or Blender 2.90.0 Alpha.
  2. Pick the Video Editing workspace.
  3. Change either the top or bottom video sequencer to "Sequencer/Preview".
  4. Press Ctrl + Spacebar to maximize the panel.
  5. Increase the size of the preview panel until it becomes large enough.
  6. Press Ctrl + Spacebar to go back to all panels.
  7. Press the spacebar key to play the timeline.
  8. Watch blender crashing.

Here is a video showing the crash procedure:

System info for 2.83.0:

System info for 2.90.0:

Related Objects

Event Timeline

ronsn added a subscriber: ronsn.Mon, Jun 22, 12:03 AM

Can not reproduce on Ubuntu 18.04 either.

System Information
Operating system: Linux-5.3.0-59-generic-x86_64-with-debian-buster-sid 64 Bits
Graphics card: GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.21

Blender Version
2.90.0 Alpha, branch: master, commit date: 2020-06-21 14:55, hash: rBf2b5f731d559

Richard Antalik (ISS) changed the task status from Needs Triage to Needs Information from User.Mon, Jun 22, 4:05 AM

Can you update your GPU driver and check if this resolves the problem?

Can you update your GPU driver and check if this resolves the problem?

Just updated to latest version and the issue still remains.

Driver 391.35 for GT 630M on Windows 10 Home. Not an issue on Ubuntu 20.04 LTS, will check driver version there as well.

Can you update your GPU driver and check if this resolves the problem?

Just updated to latest version and the issue still remains.

Driver 391.35 for GT 630M on Windows 10 Home. Not an issue on Ubuntu 20.04 LTS, will check driver version there as well.

System Information
Operating system: Linux-5.4.0-37-generic-x86_64-with-debian-bullseye-sid 64 Bits
Graphics card: GeForce GT 630M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.132

Blender Version
Worked: version: 2.83.0, branch: master, commit date: 2020-06-03 14:38, hash: rB211b6c29f771

Note: On Windows, tested both this 391.35 driver and 369.09 driver and both crashed.

FWIW no crash on macOS 10.15.5 either

Paulo Suzuki (pedropaulosuzuki) changed the task status from Needs Information from User to Needs Developer to Reproduce.Mon, Jun 22, 10:38 PM
Richard Antalik (ISS) changed the task status from Needs Developer to Reproduce to Needs Information from User.Tue, Jun 23, 8:01 AM

Can you update your GPU driver and check if this resolves the problem?

Just updated to latest version and the issue still remains.

Driver 391.35 for GT 630M on Windows 10 Home. Not an issue on Ubuntu 20.04 LTS, will check driver version there as well.

I suspect some openGL issue here not necessarily linked to VSE exclusively.

Can you run Blender from command line with -d argument? I gues it would be blender -d and paste here console output? I am not sure if it will contain stack trace in Linux, if not there will be crash.txt file mentioned in the end please upload that as well.

Can you update your GPU driver and check if this resolves the problem?

Just updated to latest version and the issue still remains.

Driver 391.35 for GT 630M on Windows 10 Home. Not an issue on Ubuntu 20.04 LTS, will check driver version there as well.

I suspect some openGL issue here not necessarily linked to VSE exclusively.

Can you run Blender from command line with -d argument? I gues it would be blender -d and paste here console output? I am not sure if it will contain stack trace in Linux, if not there will be crash.txt file mentioned in the end please upload that as well.

Here is the error I get on running Blender 2.83 with the -d flag on Windows 10 Home:

PS C:\Program Files\Blender Foundation\Blender 2.83> .\blender.exe -d
Switching to fully guarded memory allocator.
Blender 2.83.0
Build: 2020-06-03 12:41:58 Windows Release
argv[0] = C:\Program Files\Blender Foundation\Blender 2.83\blender.exe
argv[1] = -d
Read prefs: C:\Users\User\AppData\Roaming\Blender Foundation\Blender\2.83\config\userpref.blend
read file
  Version 280 sub 39 date unknown hash unknown
AL lib: (EE) UpdateDeviceParams: Failed to set 48000hz, got 44100hz instead
found bundled python: C:\Program Files\Blender Foundation\Blender 2.83\2.83\python
read file C:\Program Files\Blender Foundation\Blender 2.83\2.83\scripts\startup\bl_app_templates_system\Video_Editing\startup.blend
  Version 280 sub 39 date unknown hash unknown
Error   : EXCEPTION_ACCESS_VIOLATION
Address : 0x00007FF66000FA1C
Module  : C:\Program Files\Blender Foundation\Blender 2.83\blender.exe

Here is the terminal on Linux (no crash):

user@ubuntults:~$ blender -d --factory-startup
Switching to fully guarded memory allocator.
Blender 2.83.0
Build: 2020-06-03 14:41:25 Linux Release
argv[0] = /snap/blender/39/blender
argv[1] = -d
argv[2] = --factory-startup
read file 
  Version 280 sub 39 date unknown hash unknown
/run/user/1000/snap.blender/gvfs/ non-existent directory
found bundled python: /snap/blender/39/2.83/python
read file /snap/blender/39/2.83/scripts/startup/bl_app_templates_system/Video_Editing/startup.blend
  Version 280 sub 39 date unknown hash unknown

Could you run the debug argument with 2.90.0, there should be a stack trace attached to that.

Could you run the debug argument with 2.90.0, there should be a stack trace attached to that.

Ok!

Here is the terminal after running Blender 2.90.0 Alpha with today's build on Windows 10 Home:

PS C:\Users\User\blender-2.90.0-65006bfaf4ef-windows64> ./blender.exe -d --factory-startup
Switching to fully guarded memory allocator.
Blender 2.90.0 Alpha
Build: 2020-06-23 17:26:29 Windows Release
argv[0] = C:\Users\User\blender-2.90.0-65006bfaf4ef-windows64\blender.exe
argv[1] = -d
argv[2] = --factory-startup
read file
  Version 280 sub 39 date unknown hash unknown
found bundled python: C:\Users\User\blender-2.90.0-65006bfaf4ef-windows64\2.90\python
read file C:\Users\User\blender-2.90.0-65006bfaf4ef-windows64\2.90\scripts\startup\bl_app_templates_system\Video_Editing\startup.blend
  Version 280 sub 39 date unknown hash unknown
Error   : EXCEPTION_ACCESS_VIOLATION
Address : 0x00007FF7C9D3CE13
Module  : blender.exe
Thread  : 00000ef4
Writing: C:\Users\User\AppData\Local\Temp\blender.crash.txt

And here is the crash info with the stack trace:

Paulo Suzuki (pedropaulosuzuki) changed the task status from Needs Information from User to Needs Developer to Reproduce.Wed, Jun 24, 1:37 AM
Richard Antalik (ISS) changed the task status from Needs Developer to Reproduce to Confirmed.Wed, Jun 24, 9:27 AM
Richard Antalik (ISS) triaged this task as High priority.
Richard Antalik (ISS) changed the subtype of this task from "Report" to "Bug".

Thanks for crash file. I got confused and thought that crash was on linux.

I was able to reproduce now when running blender from command line, but I am still not able to reproduce from debugger. But that is all I need now.

I have been able to reproduce from within debugger, but only when I run with -d argument.
So far I am not sure if this is bug in tool system in general or in VSE implementation.

Exception thrown: read access violation.
area->runtime.tool was 0xFFFFFFFFFFFFFFFF.
>	blender.exe!WM_event_get_keymap_from_toolsystem_fallback(wmWindowManager * wm, wmEventHandler_Keymap * handler) Line 3657	C
 	blender.exe!wm_handlers_do_intern(bContext * C, wmEvent * event, ListBase * handlers) Line 2727	C
 	blender.exe!wm_handlers_do(bContext * C, wmEvent * event, ListBase * handlers) Line 2857	C
 	blender.exe!wm_event_do_handlers(bContext * C) Line 3360	C
 	blender.exe!WM_main(bContext * C) Line 478	C
 	blender.exe!main(int argc, const unsigned char * * UNUSED_argv_c) Line 534	C
 	[External Code]

Here is an ASAN output: P1482.

From the backtrace it seems that it might be something more generic than sequencer. @Campbell Barton (campbellbarton), @Julian Eisel (Severin), do you mind having a look here?

Thanks!!! Will this be ported to 2.83 as well? It seems to be a pretty straightforward and non code breaking patch.