blender/blender
165
521
Fork 796
Code Issues 6.8k Pull Requests 966 Projects 21 Wiki Activity

Video Sequence Editor Sequencer/Preview Crash #78112

New Issue
Closed
opened 2020-06-21 21:34:47 +02:00 by Paulo Suzuki · 28 comments
Paulo Suzuki commented 2020-06-21 21:34:47 +02:00
Copy Link

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: 211b6c29f7
Blender 2.90.0 Alpha, branch: master, commit date: 2020-06-20 22:15, hash: a7f1c68938

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:
2020-06-21 19-26-18.mkv

System info for 2.83.0:
system-info-2-83.txt

System info for 2.90.0:
system-info-2-90.txt

**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: `211b6c29f7` Blender 2.90.0 Alpha, branch: master, commit date: 2020-06-20 22:15, hash: `a7f1c68938` 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: [2020-06-21 19-26-18.mkv](https://archive.blender.org/developer/F8635529/2020-06-21_19-26-18.mkv) System info for 2.83.0: [system-info-2-83.txt](https://archive.blender.org/developer/F8635522/system-info-2-83.txt) System info for 2.90.0: [system-info-2-90.txt](https://archive.blender.org/developer/F8635524/system-info-2-90.txt)
Paulo Suzuki commented 2020-06-21 21:34:47 +02:00
Author
Copy Link

Added subscriber: @pedropaulosuzuki

Added subscriber: @pedropaulosuzuki
ronsn commented 2020-06-22 00:03:06 +02:00
Copy Link

Added subscriber: @ronsn

Added subscriber: @ronsn
ronsn commented 2020-06-22 00:03:06 +02:00
Copy Link

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: f2b5f731d5

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: `f2b5f731d5`
Richard Antalik commented 2020-06-22 04:05:47 +02:00
Member
Copy Link

Added subscriber: @iss

Added subscriber: @iss
Richard Antalik commented 2020-06-22 04:05:47 +02:00
Member
Copy Link

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

Changed status from 'Needs Triage' to: 'Needs User Info'
Richard Antalik commented 2020-06-22 04:05:47 +02:00
Member
Copy Link

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?
Paulo Suzuki commented 2020-06-22 04:09:52 +02:00
Author
Copy Link

In #78112#961806, @iss wrote:
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.

> In #78112#961806, @iss wrote: > 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.
Paulo Suzuki commented 2020-06-22 04:15:39 +02:00
Author
Copy Link

In #78112#961815, @pedropaulosuzuki wrote:

In #78112#961806, @iss wrote:
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: 211b6c29f7

> In #78112#961815, @pedropaulosuzuki wrote: >> In #78112#961806, @iss wrote: >> 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: `211b6c29f7`
Paulo Suzuki commented 2020-06-22 04:17:28 +02:00
Author
Copy Link

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

Note: On Windows, tested both this 391.35 driver and 369.09 driver and both crashed.
Andrei Nadin commented 2020-06-22 04:36:31 +02:00
Copy Link

Added subscriber: @AnadinX

Added subscriber: @AnadinX
Andrei Nadin commented 2020-06-22 04:36:31 +02:00
Copy Link

FWIW no crash on macOS 10.15.5 either

FWIW no crash on macOS 10.15.5 either
Paulo Suzuki commented 2020-06-22 22:38:33 +02:00
Author
Copy Link

Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'

Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'
Richard Antalik commented 2020-06-23 08:01:17 +02:00
Member
Copy Link

Changed status from 'Needs Developer To Reproduce' to: 'Needs User Info'

Changed status from 'Needs Developer To Reproduce' to: 'Needs User Info'
Richard Antalik commented 2020-06-23 08:01:17 +02:00
Member
Copy Link

In #78112#961815, @pedropaulosuzuki wrote:

In #78112#961806, @iss wrote:
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.

> In #78112#961815, @pedropaulosuzuki wrote: >> In #78112#961806, @iss wrote: >> 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.
Paulo Suzuki commented 2020-06-23 21:56:53 +02:00
Author
Copy Link

In #78112#962770, @iss wrote:

In #78112#961815, @pedropaulosuzuki wrote:

In #78112#961806, @iss wrote:
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
> In #78112#962770, @iss wrote: >> In #78112#961815, @pedropaulosuzuki wrote: >>> In #78112#961806, @iss wrote: >>> 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 ```
ChristopherAnderssarian commented 2020-06-23 22:10:34 +02:00
Copy Link

Added subscriber: @ChristopherAnderssarian

Added subscriber: @ChristopherAnderssarian
ChristopherAnderssarian commented 2020-06-23 22:10:34 +02:00
Copy Link

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.
Paulo Suzuki commented 2020-06-23 22:41:35 +02:00
Author
Copy Link

In #78112#963487, @ChristopherAnderssarian wrote:
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:
blender.crash.txt

> In #78112#963487, @ChristopherAnderssarian wrote: > 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: [blender.crash.txt](https://archive.blender.org/developer/F8639592/blender.crash.txt)
Paulo Suzuki commented 2020-06-24 01:37:46 +02:00
Author
Copy Link

Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'

Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'
Richard Antalik commented 2020-06-24 09:27:22 +02:00
Member
Copy Link

Changed status from 'Needs Developer To Reproduce' to: 'Confirmed'

Changed status from 'Needs Developer To Reproduce' to: 'Confirmed'
Richard Antalik commented 2020-06-24 09:27:22 +02:00
Member
Copy Link

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.

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.
Richard Antalik commented 2020-06-24 10:00:33 +02:00
Member
Copy Link

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.

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]
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] ```
Sergey Sharybin commented 2020-06-24 10:36:34 +02:00
Owner
Copy Link

Added subscribers: @JulianEisel, @ideasman42, @Sergey

Added subscribers: @JulianEisel, @ideasman42, @Sergey
Sergey Sharybin commented 2020-06-24 10:36:34 +02:00
Owner
Copy Link

Here is an ASAN output: P1482.

From the backtrace it seems that it might be something more generic than sequencer. @ideasman42, @JulianEisel, do you mind having a look here?

Here is an ASAN output: [P1482](https://archive.blender.org/developer/P1482.txt). From the backtrace it seems that it might be something more generic than sequencer. @ideasman42, @JulianEisel, do you mind having a look here?
blender-admin commented 2020-06-24 15:15:22 +02:00
Copy Link

This issue was referenced by 9a8dd8d623

This issue was referenced by 9a8dd8d62342e8e382cff42b65fd00eadcb262e1
blender-admin commented 2020-06-24 15:15:22 +02:00
Copy Link

This issue was referenced by 23b5e10dbd

This issue was referenced by 23b5e10dbd7b47553504a24afc35aa1f13bb85eb
Julian Eisel commented 2020-06-24 15:22:42 +02:00
Member
Copy Link

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Julian Eisel self-assigned this 2020-06-24 15:22:42 +02:00
Paulo Suzuki commented 2020-06-25 00:04:50 +02:00
Author
Copy Link

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

Thanks!!! Will this be ported to 2.83 as well? It seems to be a pretty straightforward and non code breaking patch.
Thomas Dinges added this to the 2.90 milestone 2023-02-08 16:27:13 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
Interest
Alembic

  
Interest
Animation & Rigging

  
Interest
Asset System
Asset datablocks, libraries, browser and shelf

  
Interest
Audio

  
Interest
Automated Testing

  
Interest
Blender Asset Bundle

  
Interest
BlendFile

  
Interest
Code Documentation
Code comments, Python/RNA API descriptions

  
Interest
Collada

  
Interest
Compatibility
Backward and forward compatibility

  
Interest
Compositing

  
Interest
Core

  
Interest
Cycles

  
Interest
Dependency Graph

  
Interest
Development Management

  
Interest
EEVEE

  
Interest
Freestyle

  
Interest
Geometry Nodes

  
Interest
Grease Pencil

  
Interest
ID Management

  
Interest
Images & Movies

  
Interest
Import Export

  
Interest
Line Art

  
Interest
Masking

  
Interest
Metal

  
Interest
Modeling

  
Interest
Modifiers

  
Interest
Motion Tracking

  
Interest
Nodes & Physics

  
Interest
OpenGL

  
Interest
Overlay

  
Interest
Overrides

  
Interest
Performance

  
Interest
Physics

  
Interest
Pipeline & IO

  
Interest
Platforms, Builds & Tests

  
Interest
Python API

  
Interest
Render & Cycles

  
Interest
Render Pipeline

  
Interest
Sculpt, Paint & Texture

  
Interest
Text Editor

  
Interest
Translations

  
Interest
Triaging

  
Interest
Undo

  
Interest
USD

  
Interest
User Interface

  
Interest
UV Editing

  
Interest
VFX & Video

  
Interest
Video Sequencer

  
Interest
Viewport & EEVEE

  
Interest
Virtual Reality

  
Interest
Vulkan

  
Interest
Wayland
Wayland windowing on Unix

  
Interest
Workbench

  
Interest: X11

Xorg/X11 windowing

  
Legacy
Asset Browser Project

Archived

  
Legacy
Blender 2.8 Project

Archived

  
Legacy
Milestone 1: Basic, Local Asset Browser

Archived

  
Legacy
OpenGL Error

Archived

  
Meta
Good First Issue

  
Meta
Papercut

  
Meta
Retrospective

  
Meta
Security
Related to security, see policy: https://developer.blender.org/docs/handbook/bug_reports/vulnerability_reports/

  
Module
Animation & Rigging

  
Module
Asset System

  
Module
Core

  
Module
Development Management

  
Module
Grease Pencil

  
Module
Modeling

  
Module
Nodes & Physics

  
Module
Pipeline & IO

  
Module
Platforms, Builds & Tests

  
Module
Python API

  
Module
Render & Cycles

  
Module
Sculpt, Paint & Texture

  
Module
Triaging

  
Module
User Interface

  
Module
VFX & Video

  
Module
Viewport & EEVEE

  
Platform
FreeBSD

  
Platform
Linux

  
Platform
macOS

  
Platform
Windows

  
Severity
High

  
Severity
Low

  
Severity
Normal

  
Severity
Unbreak Now!

  
Status
Archived

  
Status
Confirmed

  
Status
Duplicate

  
Status
Needs Info from Developers

  
Status
Needs Information from User

  
Status
Needs Triage

  
Status
Resolved

  
Type
Bug

  
Type
Design

  
Type
Known Issue

  
Type
Patch

Archived

  
Type
Report

Archived

  
Type
To Do

No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Code Documentation
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Asset System
Module
Core
Module
Development Management
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
Milestone
Clear milestone
No items
No Milestone
2.90
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
Julian Eisel
8 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#78112
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?