Resizing window causes crash on Wayland (libdecor) #107797

Open
opened 2023-05-09 20:24:04 +02:00 by Daniel Schroeder · 22 comments

System Information
Operating system: Linux-5.19.0-41-generic-x86_64-with-glibc2.35 64 Bits
Graphics card: AMD Radeon RX 5700 XT (navi10, LLVM 15.0.6, DRM 3.47, 5.19.0-41-generic) AMD 4.6 (Core Profile) Mesa 22.2.5

Blender Version
Broken: version: 3.5.1, branch: blender-v3.5-release, commit date: 2023-04-24 18:11, hash: e1ccd9d4a1d3
Worked: (unknown)

Short description of error
Rapidly resizing the Blender window causes the application to crash. If I resize the window very slowly (like, 10 or 20 pixels per second), it resizes successfully and smoothly. If I do a single, quick drag of the window edge to resize it by about 100 pixels, the window takes about a second to respond but does resize successfully. If I drag an edge or corner quickly over larger distances and for longer, the window crashes with this message in the terminal:

GHOST/Wayland: Error sending request: Broken pipe
The Wayland connection broke. Did the Wayland compositor die?
Error: Not freed memory blocks: 56580, total unfreed memory 17.653542 MB
Freeing memory after the leak detector has run. This can happen when using static variables in C++ that are defined outside of functions. To fix this error, use the 'construct on first use' idiom.
Freeing memory after the leak detector has run. This can happen when using static variables in C++ that are defined outside of functions. To fix this error, use the 'construct on first use' idiom.
Freeing memory after the leak detector has run. This can happen when using static variables in C++ that are defined outside of functions. To fix this error, use the 'construct on first use' idiom.
[... etc. ...]

Exact steps for others to reproduce the error

  • Install Blender on Ubuntu 22.04.2 LTS from the official snap (https://snapcraft.io/blender)
  • Open Blender while running in a default Wayland login
  • Un-maximize the window, click and drag on a corner to resize the window, and move the mouse rapidly over large distances
**System Information** Operating system: Linux-5.19.0-41-generic-x86_64-with-glibc2.35 64 Bits Graphics card: AMD Radeon RX 5700 XT (navi10, LLVM 15.0.6, DRM 3.47, 5.19.0-41-generic) AMD 4.6 (Core Profile) Mesa 22.2.5 **Blender Version** Broken: version: 3.5.1, branch: blender-v3.5-release, commit date: 2023-04-24 18:11, hash: `e1ccd9d4a1d3` Worked: (unknown) **Short description of error** Rapidly resizing the Blender window causes the application to crash. If I resize the window *very* slowly (like, 10 or 20 pixels per second), it resizes successfully and smoothly. If I do a single, quick drag of the window edge to resize it by about 100 pixels, the window takes about a second to respond but does resize successfully. If I drag an edge or corner quickly over larger distances and for longer, the window crashes with this message in the terminal: GHOST/Wayland: Error sending request: Broken pipe The Wayland connection broke. Did the Wayland compositor die? Error: Not freed memory blocks: 56580, total unfreed memory 17.653542 MB Freeing memory after the leak detector has run. This can happen when using static variables in C++ that are defined outside of functions. To fix this error, use the 'construct on first use' idiom. Freeing memory after the leak detector has run. This can happen when using static variables in C++ that are defined outside of functions. To fix this error, use the 'construct on first use' idiom. Freeing memory after the leak detector has run. This can happen when using static variables in C++ that are defined outside of functions. To fix this error, use the 'construct on first use' idiom. [... etc. ...] **Exact steps for others to reproduce the error** - Install Blender on Ubuntu 22.04.2 LTS from the official snap (https://snapcraft.io/blender) - Open Blender while running in a default Wayland login - Un-maximize the window, click and drag on a corner to resize the window, and move the mouse rapidly over large distances
Daniel Schroeder added the
Severity
Normal
Type
Report
Status
Needs Triage
labels 2023-05-09 20:24:05 +02:00
Iliya Katushenock added the
Interest
User Interface
Interest
Wayland
labels 2023-05-09 20:24:46 +02:00

Confirmed the same behavior on the current stable and alpha daily builds:

  • version: 3.5.1, branch: blender-v3.5-release, commit date: 2023-04-25 13:50, hash: 6ee8aa4997ee
  • version: 3.6.0 Alpha, branch: main, commit date: 2023-05-09 15:20, hash: 521e79b86912
Confirmed the same behavior on the current stable and alpha daily builds: - version: 3.5.1, branch: blender-v3.5-release, commit date: 2023-04-25 13:50, hash: `6ee8aa4997ee` - version: 3.6.0 Alpha, branch: main, commit date: 2023-05-09 15:20, hash: `521e79b86912`

One more quick update: the crash does not occur if I request an Xorg session on the Ubuntu login screen. Additionally, several other applications experience very laggy window resizing under Wayland but not Xorg (e.g., VLC, GIMP), but none of them crash in response to window resize.

One more quick update: the crash does *not* occur if I request an Xorg session on the Ubuntu login screen. Additionally, several other applications experience very laggy window resizing under Wayland but not Xorg (e.g., VLC, GIMP), but none of them crash in response to window resize.

Just chiming in with my own test of this. I haven't been able to crash a session even with some very fast window resizing. It resizes quite fast actually. I would say faster than most apps so I don't think I observe this same behavior of having a sluggish resize response time.

I'm on:

Ubuntu 23.04
Linux 6.2.0-20-generic x86_64
Wayland
AMD RX 570 GPU
Tested on official snap install and main (e151425c5c1 from 2023-05-08)

Just chiming in with my own test of this. I haven't been able to crash a session even with some very fast window resizing. It resizes quite fast actually. I would say faster than most apps so I don't think I observe this same behavior of having a sluggish resize response time. I'm on: > Ubuntu 23.04 > Linux 6.2.0-20-generic x86_64 > Wayland > AMD RX 570 GPU > Tested on official snap install and `main` (`e151425c5c1` from 2023-05-08)
Member

It's weird that I experience very laggy window resizing under X but not on wayland.

It's weird that I experience very laggy window resizing under X but not on wayland.
Member

Cannot repro here

**System Information**
Operating system: Linux-6.1.18-200.fc37.x86_64-x86_64-with-glibc2.36 64 Bits
Graphics card: AMD Radeon Graphics (renoir, LLVM 15.0.7, DRM 3.49, 6.1.18-200.fc37.x86_64) AMD 4.6 (Core Profile) Mesa 22.3.7
version: 3.5.1, branch: blender-v3.5-release, commit date: 2023-04-24 18:11, hash: `e1ccd9d4a1d3`

@ideasman42 : are you able to repro?

Cannot repro here ``` **System Information** Operating system: Linux-6.1.18-200.fc37.x86_64-x86_64-with-glibc2.36 64 Bits Graphics card: AMD Radeon Graphics (renoir, LLVM 15.0.7, DRM 3.49, 6.1.18-200.fc37.x86_64) AMD 4.6 (Core Profile) Mesa 22.3.7 version: 3.5.1, branch: blender-v3.5-release, commit date: 2023-04-24 18:11, hash: `e1ccd9d4a1d3` ``` @ideasman42 : are you able to repro?

I can't redo the bug either. Things to look into:

  • Test on a different compositor (KDE/SWAY for example) most other compositors support server-side decorations. This issue could be related to libdecor (which handles decorations).

  • Test on GNOME with libdecor disabled (possible since: a9358f5274), included in the latest 4.0 alpha daily build.

    • Uninstall libdecor.
    • Run DISPLAY="" ./blender

    This will run Blender without libdecor so you can check if this causes the error.

I can't redo the bug either. Things to look into: - Test on a different compositor (KDE/SWAY for example) most other compositors support server-side decorations. This issue could be related to libdecor (which handles decorations). - Test on GNOME with libdecor disabled (possible since: a9358f5274b60c61a5a2a57389372d01ade9be5a), included in the latest 4.0 alpha daily build. - Uninstall `libdecor`. - Run `DISPLAY="" ./blender` This will run Blender without libdecor so you can check if this causes the error.
Member

I can't redo the bug either. Things to look into:

  • Test on a different compositor (KDE/SWAY for example) most other compositors support server-side decorations. This issue could be related to libdecor (which handles decorations).

  • Test on GNOME with libdecor disabled (possible since: a9358f5274), included in the latest 4.0 alpha daily build.

    • Uninstall libdecor.
    • Run DISPLAY="" ./blender

    This will run Blender without libdecor so you can check if this causes the error.

@dan5sch : do you have a chance to test the above?

> I can't redo the bug either. Things to look into: > > - Test on a different compositor (KDE/SWAY for example) most other compositors support server-side decorations. This issue could be related to libdecor (which handles decorations). > - Test on GNOME with libdecor disabled (possible since: a9358f5274b60c61a5a2a57389372d01ade9be5a), included in the latest 4.0 alpha daily build. > > - Uninstall `libdecor`. > - Run `DISPLAY="" ./blender` > > This will run Blender without libdecor so you can check if this causes the error. > @dan5sch : do you have a chance to test the above?
Philipp Oeser added
Status
Needs Information from User
and removed
Status
Needs Triage
labels 2023-07-19 13:39:14 +02:00

@lichtwerk I haven't. I use this machine for my work, so I'm wary of mucking with the installation of the desktop environment itself.

@lichtwerk I haven't. I use this machine for my work, so I'm wary of mucking with the installation of the desktop environment itself.

@dan5sch: Running with DISPLAY="" ./blender doesn't require system modifications, could you please test this?

@dan5sch: Running with `DISPLAY="" ./blender` doesn't require system modifications, could you please test this?
Campbell Barton changed title from Resizing window causes crash to Resizing window causes crash on Wayland 2023-07-21 01:22:03 +02:00

@ideasman42 running Blender with DISPLAY="" in a Wayland Gnome session still crashed when I resized the window quickly. (To be clear, this was without uninstalling libdecor or any of the other steps in your original comment.)

@ideasman42 running Blender with `DISPLAY=""` in a Wayland Gnome session still crashed when I resized the window quickly. (To be clear, this was without uninstalling `libdecor` or any of the other steps in your original comment.)

@dan5sch: hang on, you would have to make sure libdecor isn't available for this to work as expected.

@dan5sch: hang on, you would have to make sure libdecor isn't available for this to work as expected.

@ideasman42 OK, found a way to test this. TL;DR: DISPLAY="" blender does NOT crash on rapid resize when loading of libdecor is prevented.

Method:
Using the approach in this post, I was able to LD_PRELOAD a modified dlopen() that prevents loading libdecor. To my pleasant surprise, this just worked.

Results (again in Wayland Gnome):

  • blender: crash on rapid window resize. xwininfo does NOT say Blender is an X window.
  • LD_PRELOAD=libmydlopen.so blender: Window decorations resemble those of "native" Gnome 3 applications. NO crash on rapid window resize. xwininfo says that Blender is an X window.
  • DISPLAY="" LD_PRELOAD=libmydlopen.so blender: NO window decorations at all. NO crash on rapid window resize after using ALT-F8 to enable resize with the mouse. xwininfo says that Blender is NOT an X window.
@ideasman42 OK, found a way to test this. TL;DR: `DISPLAY="" blender` does NOT crash on rapid resize when loading of `libdecor` is prevented. Method: Using the approach in [this post](https://stackoverflow.com/a/47611414), I was able to `LD_PRELOAD` a modified `dlopen()` that prevents loading `libdecor`. To my pleasant surprise, this just worked. Results (again in Wayland Gnome): - `blender`: crash on rapid window resize. `xwininfo` does NOT say Blender is an X window. - `LD_PRELOAD=libmydlopen.so blender`: Window decorations resemble those of "native" Gnome 3 applications. NO crash on rapid window resize. `xwininfo` says that Blender is an X window. - `DISPLAY="" LD_PRELOAD=libmydlopen.so blender`: NO window decorations at all. NO crash on rapid window resize after using `ALT-F8` to enable resize with the mouse. `xwininfo` says that Blender is NOT an X window.
Member

OK, thx getting back.

@ideasman42 : what would be the way forward here then?

OK, thx getting back. @ideasman42 : what would be the way forward here then?
Philipp Oeser changed title from Resizing window causes crash on Wayland to Resizing window causes crash on Wayland (libdecor) 2023-08-15 12:17:17 +02:00

@lichtwerk I can't redo this bug reliably although I did manage to get a crash once.
I'm not all that satisfied with libdecor, there are currently 3 open issues relating to libdecor where I'm not sure how we might proceed, although this crash is the worst.

For reference the 2 other bugs: #109194, #108308.


So longer term it may be best to use client side decorations, although if this crash can be reproduced reliably by a developer it should be investigated of course.

@lichtwerk I can't redo this bug reliably although I did manage to get a crash once. I'm not all that satisfied with libdecor, there are currently 3 open issues relating to libdecor where I'm not sure how we might proceed, although this crash is the worst. For reference the 2 other bugs: #109194, #108308. --- So longer term it may be best to use client side decorations, although if this crash can be reproduced reliably by a developer it should be investigated of course.

Attempting to redo this crash and I wasn't able to - gnome-shell 44.3.

Unless a developer can redo the issue it doesn't seem likely it can be resolved.

Attempting to redo this crash and I wasn't able to - gnome-shell 44.3. Unless a developer can redo the issue it doesn't seem likely it can be resolved.

@dan5sch could you check if this is resolved by recent builds? (it's possible e1dac0b122 fixes the bug).

@dan5sch could you check if this is resolved by recent builds? (it's possible e1dac0b1225eb498524811d12fb1561eef3407b5 fixes the bug).
Campbell Barton added
Status
Needs Information from User
and removed
Status
Needs Info from Developers
labels 2023-10-06 08:37:33 +02:00

@ideasman42 tested today's alpha build f3f494fd63 which is now past the commit e1dac0b122 you mentioned. Results:

  • Crashing: it is now much harder to crash Blender by dragging a window corner and resizing. Crashes only occur after several seconds of dragging and rapidly moving the mouse large distances; and only some attempts trigger a crash.
  • Lag: while dragging a window corner rapidly, the window updates its displayed size at only single-digit framerates (or not at all for over a second before a crash). But so do several other applications on this system under Wayland (despite good system specs, and those applications resizing quickly under Xorg).

Notably, a new bug has appeared: if I begin dragging a corner of the window, move the mouse rapidly, and release the left mouse button while the mouse is still moving rapidly, the dimensions of the displayed window contents and the displayed window decoration / drop shadow appear to disagree with one another by one frame of mouse movement. Examples:

Screenshot from 2023-10-07 13-44-47.png
Screenshot from 2023-10-07 13-44-35.png

In this state:

  • the bottom right corner of the drop shadow displays a resize cursor on hover and responds to resize click-drag inputs; as soon as I begin resizing, the window contents snap to the dimensions of the drop shadow
  • if I interact with the window contents region with the mouse, the region redraws (e.g., rotating the viewport camera) without changing its dimensions to match the drop shadow
  • moving the window by dragging the title bar does not remove the glitched state
  • alt-tabbing away from the Blender window and then back removes the glitched state
@ideasman42 tested today's alpha build f3f494fd63aa which is now past the commit e1dac0b122 you mentioned. Results: - Crashing: it is now *much* harder to crash Blender by dragging a window corner and resizing. Crashes only occur after several seconds of dragging and rapidly moving the mouse large distances; and only some attempts trigger a crash. - Lag: while dragging a window corner rapidly, the window updates its displayed size at only single-digit framerates (or not at all for over a second before a crash). But so do several other applications on this system under Wayland (despite good system specs, and those applications resizing quickly under Xorg). Notably, a *new* bug has appeared: if I begin dragging a corner of the window, move the mouse rapidly, and release the left mouse button while the mouse is still moving rapidly, the dimensions of the displayed window contents and the displayed window decoration / drop shadow appear to disagree with one another by one frame of mouse movement. Examples: ![Screenshot from 2023-10-07 13-44-47.png](/attachments/6d9e9a8d-cf18-4c61-966a-637b24b8a2b2) ![Screenshot from 2023-10-07 13-44-35.png](/attachments/4fa3b9b9-288f-4b3a-921e-0f547ae1e950) In this state: - the bottom right corner of the *drop shadow* displays a resize cursor on hover and responds to resize click-drag inputs; as soon as I begin resizing, the window contents snap to the dimensions of the drop shadow - if I interact with the window *contents* region with the mouse, the region redraws (e.g., rotating the viewport camera) *without* changing its dimensions to match the drop shadow - moving the window by dragging the title bar does *not* remove the glitched state - alt-tabbing away from the Blender window and then back removes the glitched state

@dan5sch thanks for checking: could you please note which versions of gnome-shell & libdecor your using?
I'm on: GNOME Shell 44.5, libdecor 0.2.0.

It may be that this issue only happens on older versions of both.
Note that I was concerned about e1dac0b122 causing the issue you described with the border getting out of sync with the window but I wasn't able to trigger this problem, so it's unfortunate this happens for some configurations.

@dan5sch thanks for checking: could you please note which versions of gnome-shell & libdecor your using? I'm on: GNOME Shell 44.5, libdecor 0.2.0. It may be that this issue only happens on older versions of both. Note that I was concerned about e1dac0b122 causing the issue you described with the border getting out of sync with the window but I wasn't able to trigger this problem, so it's unfortunate this happens for some configurations.

@ideasman42 GNOME Shell 42.9, libdecor 0.1.0

These are the versions provided by Ubuntu 22.04.3 LTS.

@ideasman42 GNOME Shell 42.9, libdecor 0.1.0 These are the versions provided by Ubuntu 22.04.3 LTS.
Philipp Oeser added
Status
Needs Triage
and removed
Status
Needs Information from User
labels 2023-10-24 09:48:19 +02:00

@dan5sch could you please check if this is resolved in recent builds, it's possible 1455315111 resolves the problem.

@dan5sch could you please check if this is resolved in recent builds, it's possible 1455315111ae769d101413fe600662484ff46d62 resolves the problem.
Campbell Barton added
Status
Needs Information from User
and removed
Status
Needs Triage
labels 2023-12-17 08:35:02 +01:00

@ideasman42 tested the latest alpha build 29b5919ad1 which is past 1455315111. Same GNOME Shell / libdecor versions as last test (from system repos).

Blender continues to crash after about two seconds of rapidly resizing the window. The non-crash failure mode described in my previous reply (with the screenshots) no longer occurs.

New since my original bug report is that the program displays a stack trace upon crashing. Pasting it in case it's useful.

GHOST/Wayland: Error sending request: Broken pipe
./blender() [0xf5f210]
/lib/x86_64-linux-gnu/libwayland-client.so.0(+0x595a) [0x7fa8bfe3d95a]
/lib/x86_64-linux-gnu/libwayland-client.so.0(wl_proxy_marshal_array_flags+0x46d) [0x7fa8bfe412bd]
/lib/x86_64-linux-gnu/libwayland-client.so.0(wl_proxy_marshal_flags+0xef) [0x7fa8bfe41c7f]
/usr/lib/x86_64-linux-gnu/libdecor/plugins-1/libdecor-cairo.so(+0x7283) [0x7fa8d52c8283]
/usr/lib/x86_64-linux-gnu/libdecor/plugins-1/libdecor-cairo.so(+0x7bfd) [0x7fa8d52c8bfd]
/usr/lib/x86_64-linux-gnu/libdecor/plugins-1/libdecor-cairo.so(+0x7de6) [0x7fa8d52c8de6]
/lib/x86_64-linux-gnu/libdecor-0.so.0(libdecor_frame_commit+0x8d) [0x7fa8bfe28a5d]
./blender() [0x289a919]
./blender() [0x289ace3]
/lib/x86_64-linux-gnu/libdecor-0.so.0(+0x37ec) [0x7fa8bfe277ec]
/lib/x86_64-linux-gnu/libffi.so.8(+0x7e2e) [0x7fa8bfe08e2e]
/lib/x86_64-linux-gnu/libffi.so.8(+0x4493) [0x7fa8bfe05493]
/lib/x86_64-linux-gnu/libwayland-client.so.0(+0x6ad0) [0x7fa8bfe3ead0]
/lib/x86_64-linux-gnu/libwayland-client.so.0(+0x7243) [0x7fa8bfe3f243]
/lib/x86_64-linux-gnu/libwayland-client.so.0(wl_display_dispatch_queue_pending+0x7c) [0x7fa8bfe3f43c]
./blender() [0x2891b4e]
./blender() [0xfd5e1d]
./blender() [0xfa4218]
./blender() [0x72662d]
/lib/x86_64-linux-gnu/libc.so.6(+0x29d90) [0x7fa8c3429d90]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x80) [0x7fa8c3429e40]
./blender() [0x8c076e]
The Wayland connection broke. Did the Wayland compositor die?
@ideasman42 tested the latest alpha build 29b5919ad11a which is past 1455315111. Same GNOME Shell / libdecor versions as last test (from system repos). Blender continues to crash after about two seconds of rapidly resizing the window. The non-crash failure mode described in my previous reply (with the screenshots) no longer occurs. New since my original bug report is that the program displays a stack trace upon crashing. Pasting it in case it's useful. ``` GHOST/Wayland: Error sending request: Broken pipe ./blender() [0xf5f210] /lib/x86_64-linux-gnu/libwayland-client.so.0(+0x595a) [0x7fa8bfe3d95a] /lib/x86_64-linux-gnu/libwayland-client.so.0(wl_proxy_marshal_array_flags+0x46d) [0x7fa8bfe412bd] /lib/x86_64-linux-gnu/libwayland-client.so.0(wl_proxy_marshal_flags+0xef) [0x7fa8bfe41c7f] /usr/lib/x86_64-linux-gnu/libdecor/plugins-1/libdecor-cairo.so(+0x7283) [0x7fa8d52c8283] /usr/lib/x86_64-linux-gnu/libdecor/plugins-1/libdecor-cairo.so(+0x7bfd) [0x7fa8d52c8bfd] /usr/lib/x86_64-linux-gnu/libdecor/plugins-1/libdecor-cairo.so(+0x7de6) [0x7fa8d52c8de6] /lib/x86_64-linux-gnu/libdecor-0.so.0(libdecor_frame_commit+0x8d) [0x7fa8bfe28a5d] ./blender() [0x289a919] ./blender() [0x289ace3] /lib/x86_64-linux-gnu/libdecor-0.so.0(+0x37ec) [0x7fa8bfe277ec] /lib/x86_64-linux-gnu/libffi.so.8(+0x7e2e) [0x7fa8bfe08e2e] /lib/x86_64-linux-gnu/libffi.so.8(+0x4493) [0x7fa8bfe05493] /lib/x86_64-linux-gnu/libwayland-client.so.0(+0x6ad0) [0x7fa8bfe3ead0] /lib/x86_64-linux-gnu/libwayland-client.so.0(+0x7243) [0x7fa8bfe3f243] /lib/x86_64-linux-gnu/libwayland-client.so.0(wl_display_dispatch_queue_pending+0x7c) [0x7fa8bfe3f43c] ./blender() [0x2891b4e] ./blender() [0xfd5e1d] ./blender() [0xfa4218] ./blender() [0x72662d] /lib/x86_64-linux-gnu/libc.so.6(+0x29d90) [0x7fa8c3429d90] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x80) [0x7fa8c3429e40] ./blender() [0x8c076e] The Wayland connection broke. Did the Wayland compositor die? ```

@dan5sch since the issue is a broken pipe in libdecor's code, it looks as if the connection is being lost outside of Blender, I'm not sure if this is something we can fix.

@dan5sch since the issue is a broken pipe in libdecor's code, it looks as if the connection is being lost outside of Blender, I'm not sure if this is something we can fix.
Bart van der Braak added
Type
Bug
and removed
Type
Report
labels 2024-08-14 13:12:45 +02:00
Sign in to join this conversation.
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, Assets & 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
Core
Module
Development Management
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & 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
No Milestone
No project
No Assignees
5 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#107797
No description provided.