Blender often crashes with xcb-related error messages #90247

New Issue

Alexander Ewering · 2021-07-27T21:36:23+02:00

Alexander Ewering commented

2021-07-27 21:36:23 +02:00

System Information
Operating system: Manjaro Linux (current) on X11 (KDE Plasma)
Graphics card: Intel HD Graphics 3000 (Mesa drivers)

Blender Version
Broken: 2.93.1

Short description of error
After a fresh install, Blender often crashes with xcb-related errors. Sometimes immediately after launch (after the UI shows briefly), sometimes when opening Edit -> Preferences.

Console output at moment of crash:

[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
blender: xcb_io.c:269: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.

It seems like this bug is most often triggered when an additional window is opened (preferences, render, etc.)

**System Information** Operating system: Manjaro Linux (current) on X11 (KDE Plasma) Graphics card: Intel HD Graphics 3000 (Mesa drivers) **Blender Version** Broken: 2.93.1 **Short description of error** After a fresh install, Blender often crashes with xcb-related errors. Sometimes immediately after launch (after the UI shows briefly), sometimes when opening Edit -> Preferences. Console output at moment of crash: [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. blender: xcb_io.c:269: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. It seems like this bug is most often triggered when an additional window is opened (preferences, render, etc.)

Alexander Ewering commented

2021-07-27 21:36:23 +02:00

Added subscriber: @intrr

blender-admin commented

2021-07-27 21:36:23 +02:00

#91918 was marked as duplicate of this issue

blender-admin commented

2021-07-27 21:36:23 +02:00

#90813 was marked as duplicate of this issue

Scurest commented

2021-07-27 22:40:01 +02:00

Added subscriber: @scurest

Evan Wilson commented

2021-07-28 02:05:52 +02:00

Added subscriber: @EAW

Evan Wilson commented

2021-07-28 02:05:52 +02:00

Triaging Note: This comment describing the cause and fix of the same xcb error in this repository might be helpful.
https://github.com/rust-windowing/winit/issues/458#issuecomment-395132897

Triaging Note: This comment describing the cause and fix of the same xcb error in this repository might be helpful. https://github.com/rust-windowing/winit/issues/458#issuecomment-395132897

Richard Antalik commented

2021-08-06 03:40:24 +02:00

Added subscribers: @lichtwerk, @iss

Richard Antalik commented

2021-08-06 03:40:24 +02:00

I am not really familiar in X11 system and how we interface with that, but this doesn't sound like Blender bug. Not sure even what would be the best place to report this issue.
@lichtwerk any idea?

I am not really familiar in X11 system and how we interface with that, but this doesn't sound like Blender bug. Not sure even what would be the best place to report this issue. @lichtwerk any idea?

Alexander Ewering commented

2021-08-07 20:30:05 +02:00

Backtrace of crash in GDB immediately after hitting F12 (render), in case it helps.

[Thread 0x7fffb27fe640 (LWP 1571) exited]
[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
blender: xcb_io.c:269: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.

Thread 1 "blender" received signal SIGABRT, Aborted.
0x00007fffed087d22 in raise () from /usr/lib/libc.so.6
(gdb) bt
- 0  0x00007fffed087d22 in raise () at /usr/lib/libc.so.6
- 1  0x00007fffed071862 in abort () at /usr/lib/libc.so.6
- 2  0x00007fffed071747 in _nl_load_domain.cold () at /usr/lib/libc.so.6
- 3  0x00007fffed080616 in  () at /usr/lib/libc.so.6
- 4  0x00007ffff7b8dd2d in  () at /usr/lib/libX11.so.6
- 5  0x00007ffff7b8ddc8 in  () at /usr/lib/libX11.so.6
- 6  0x00007ffff7b8e182 in _XEventsQueued () at /usr/lib/libX11.so.6
- 7  0x00007ffff7b91176 in _XGetRequest () at /usr/lib/libX11.so.6
- 8  0x00007ffff7b7c395 in XNoOp () at /usr/lib/libX11.so.6
- 9  0x00007fffb96ae6e3 in  () at /usr/lib/libGLX_mesa.so.0
- 10 0x00007fffe2c07428 in  () at /usr/lib/libGLX.so.0
- 11 0x00005555574ada7a in GHOST_ContextGLX::initializeDrawingContext() ()
- 12 0x00005555574accf4 in GHOST_WindowX11::newDrawingContext(GHOST_TDrawingContextType) ()
- 13 0x00005555574b4bcd in GHOST_Window::setDrawingContextType(GHOST_TDrawingContextType) ()
- 14 0x00005555574ac2da in GHOST_WindowX11::GHOST_WindowX11(GHOST_SystemX11*, _XDisplay*, char const*, int, int, unsigned int, unsigned int, GHOST_TWindowState, GHOST_WindowX11*, GHOST_TDrawingContextType, bool, bool, bool, bool, bool) ()
- 15 0x00005555574a90b3 in GHOST_SystemX11::createWindow(char const*, int, int, unsigned int, unsigned int, GHOST_TWindowState, GHOST_TDrawingContextType, GHOST_GLSettings, bool, bool, GHOST_IWindow const*) ()
- 16 0x00005555574a2dde in GHOST_CreateWindow ()
- 17 0x0000555556804a73 in wm_window_ghostwindow_ensure ()
- 18 0x0000555556805110 in WM_window_open ()
- 19 0x000055555793e97b in render_view_open ()
- 20 0x0000555557936ade in screen_render_invoke ()
- 21 0x00005555567d9f83 in wm_operator_invoke.part ()
- 22 0x00005555567dd3d7 in wm_handler_operator_call ()
- 23 0x00005555567de7a1 in wm_handlers_do_intern ()
- 24 0x00005555567ded6c in wm_handlers_do ()
- 25 0x00005555567df9d0 in wm_event_do_handlers ()
- 26 0x00005555567d51a2 in WM_main ()
- 27 0x00005555563b4420 in main ()
(gdb)

Backtrace of crash in GDB immediately after hitting F12 (render), in case it helps. ``` [Thread 0x7fffb27fe640 (LWP 1571) exited] [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. blender: xcb_io.c:269: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. Thread 1 "blender" received signal SIGABRT, Aborted. 0x00007fffed087d22 in raise () from /usr/lib/libc.so.6 (gdb) bt - 0 0x00007fffed087d22 in raise () at /usr/lib/libc.so.6 - 1 0x00007fffed071862 in abort () at /usr/lib/libc.so.6 - 2 0x00007fffed071747 in _nl_load_domain.cold () at /usr/lib/libc.so.6 - 3 0x00007fffed080616 in () at /usr/lib/libc.so.6 - 4 0x00007ffff7b8dd2d in () at /usr/lib/libX11.so.6 - 5 0x00007ffff7b8ddc8 in () at /usr/lib/libX11.so.6 - 6 0x00007ffff7b8e182 in _XEventsQueued () at /usr/lib/libX11.so.6 - 7 0x00007ffff7b91176 in _XGetRequest () at /usr/lib/libX11.so.6 - 8 0x00007ffff7b7c395 in XNoOp () at /usr/lib/libX11.so.6 - 9 0x00007fffb96ae6e3 in () at /usr/lib/libGLX_mesa.so.0 - 10 0x00007fffe2c07428 in () at /usr/lib/libGLX.so.0 - 11 0x00005555574ada7a in GHOST_ContextGLX::initializeDrawingContext() () - 12 0x00005555574accf4 in GHOST_WindowX11::newDrawingContext(GHOST_TDrawingContextType) () - 13 0x00005555574b4bcd in GHOST_Window::setDrawingContextType(GHOST_TDrawingContextType) () - 14 0x00005555574ac2da in GHOST_WindowX11::GHOST_WindowX11(GHOST_SystemX11*, _XDisplay*, char const*, int, int, unsigned int, unsigned int, GHOST_TWindowState, GHOST_WindowX11*, GHOST_TDrawingContextType, bool, bool, bool, bool, bool) () - 15 0x00005555574a90b3 in GHOST_SystemX11::createWindow(char const*, int, int, unsigned int, unsigned int, GHOST_TWindowState, GHOST_TDrawingContextType, GHOST_GLSettings, bool, bool, GHOST_IWindow const*) () - 16 0x00005555574a2dde in GHOST_CreateWindow () - 17 0x0000555556804a73 in wm_window_ghostwindow_ensure () - 18 0x0000555556805110 in WM_window_open () - 19 0x000055555793e97b in render_view_open () - 20 0x0000555557936ade in screen_render_invoke () - 21 0x00005555567d9f83 in wm_operator_invoke.part () - 22 0x00005555567dd3d7 in wm_handler_operator_call () - 23 0x00005555567de7a1 in wm_handlers_do_intern () - 24 0x00005555567ded6c in wm_handlers_do () - 25 0x00005555567df9d0 in wm_event_do_handlers () - 26 0x00005555567d51a2 in WM_main () - 27 0x00005555563b4420 in main () (gdb) ```

Pratik Borhade commented

2021-08-24 09:05:34 +02:00

Added subscribers: @Evan-9, @PratikPB2123, @arrow_x86

Leo commented

2021-08-30 20:31:02 +02:00

Added subscriber: @leoplaw

Leo commented

2021-08-30 20:36:19 +02:00

I am seeing the same crash intermittently, with Blender 2.93 and 3.0 alpha.

Operating System: openSUSE Tumbleweed 20210515
KDE Plasma Version: 5.21.5
KDE Frameworks Version: 5.82.0
Qt Version: 5.15.2
Kernel Version: 5.13.1-1-default
OS Type: 64-bit
Graphics Platform: X11
Processors: 32 × Intel® Xeon® CPU E5-2690 0 @ 2.90GHz
Memory: 62.7 GiB of RAM
Graphics Processor: AMD CEDAR

I am seeing the same crash intermittently, with Blender 2.93 and 3.0 alpha. Operating System: openSUSE Tumbleweed 20210515 KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.13.1-1-default OS Type: 64-bit Graphics Platform: X11 Processors: 32 × Intel® Xeon® CPU E5-2690 0 @ 2.90GHz Memory: 62.7 GiB of RAM Graphics Processor: AMD CEDAR

Andrew Smirnov commented

2021-09-10 00:29:25 +02:00

Added subscriber: @Ponchman

DiRK commented

2021-09-17 12:43:28 +02:00

Added subscriber: @3DiRK

Richard Antalik commented

2021-10-04 00:27:17 +02:00

Added subscriber: @leonidussaks

Dennis commented

2021-11-27 05:43:15 +01:00

Added subscriber: @blendear

Dennis commented

2021-11-27 05:43:15 +01:00

Kubuntu 21.10
KDE Plasma Version: 5.22.5 / KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2 / Kernel Version: 5.13.0-21-generic (64-bit)

Same here. Any additional window (save,import,export,prefs) crashes blender with ~75-80% percent probability making it totally unusable.
Also all past versions are affected now too back to 2.83 (I stopped trying at that point) so I can't even fall back.
Since I have a pretty vanilla system (Ubuntu+KDE) I expect this bug to affect lots of users.

Some info I found:

Apparently this bug crashes lots of GTK2 applications.
Considering past versions of Blender are crashing now too (which were very stable on my system), I guess this is not related to a change in Blender itself.
Interesting thing is, the following thread goes back to 2018. Why did this bug catch Blender now ?

FreeCAD, Libreoffice, Pidgin, GIMP are some of the other crashing apps with the same error message in this thread:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710

A comment from that thread:

The bug does not manifest itself if there is only one active CPU core. The number of active CPU cores can be controlled by 'maxcpus' kernel parameter: add 'maxcpus=1' to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub, then run update-grub as root.

Also it happens on the ARM platform too it seems:
https://community.arm.com/support-forums/f/graphics-gaming-and-vr-forum/5914/xcb-most-likely-this-is-a-multi-threaded-client-and-xinitthreads-has-not-been-called
Explanation from that thread:

The Mali userspace blob (libMali.so) has issues with threading. It uses threading internally but doesn't call XInitThreads early, which leads to problems.
Or because all multithread Xorg application need call XInitThreads before any work with Xorg. libMali implicitly uses threads and call XInitThreads too later.

Kubuntu 21.10 KDE Plasma Version: 5.22.5 / KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 / Kernel Version: 5.13.0-21-generic (64-bit) --- Same here. Any additional window (save,import,export,prefs) crashes blender with ~75-80% percent probability making it totally unusable. Also all past versions are affected now too back to 2.83 (I stopped trying at that point) so I can't even fall back. Since I have a pretty vanilla system (Ubuntu+KDE) I expect this bug to affect lots of users. **Some info I found:** - Apparently this bug crashes lots of GTK2 applications. Considering past versions of Blender are crashing now too (which were very stable on my system), I guess this is not related to a change in Blender itself. Interesting thing is, the following thread goes back to 2018. Why did this bug catch Blender now ? FreeCAD, Libreoffice, Pidgin, GIMP are some of the other crashing apps with the same error message in this thread: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710 A comment from that thread: > The bug does not manifest itself if there is only one active CPU core. The number of active CPU cores can be controlled by 'maxcpus' kernel parameter: add 'maxcpus=1' to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub, then run update-grub as root. - Also it happens on the ARM platform too it seems: https://community.arm.com/support-forums/f/graphics-gaming-and-vr-forum/5914/xcb-most-likely-this-is-a-multi-threaded-client-and-xinitthreads-has-not-been-called Explanation from that thread: > The Mali userspace blob (libMali.so) has issues with threading. It uses threading internally but doesn't call XInitThreads early, which leads to problems. > Or because all multithread Xorg application need call XInitThreads before any work with Xorg. libMali implicitly uses threads and call XInitThreads too later.

Dennis commented

2021-12-07 01:58:35 +01:00

I confirm this crashing situation is the same in BLENDER 3.0 too (not surprising considering it is GTK related).
Anyone has a suggestion for a solution ?
How other people are even using Blender now with this bug ?


[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
blender: ../../src/xcb_io.c:269: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.

I confirm this crashing situation is the same in **BLENDER 3.0** too (not surprising considering it is GTK related). Anyone has a suggestion for a solution ? How other people are even using Blender now with this bug ? ``` [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. blender: ../../src/xcb_io.c:269: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. ```

Aaron Carlisle commented

2021-12-07 02:09:50 +01:00

Added subscriber: @Blendify

Aaron Carlisle commented

2021-12-07 02:09:50 +01:00

The issue was fixed upstream in LibX11 see 58a52fcbf6

I suppose this requires updating the library on the build bots? Im not sure how we handle the version of libx11 we build with

The issue was fixed upstream in LibX11 see https://gitlab.freedesktop.org/xorg/lib/libx11/-/commit/58a52fcbf698895f46d7e141cc162593c1f1218f I suppose this requires updating the library on the build bots? Im not sure how we handle the version of libx11 we build with

SpaceOne commented

2022-01-04 11:09:23 +01:00

Added subscriber: @SpaceOne

SpaceOne commented

2022-01-04 11:09:23 +01:00

I also had the exact same problem when opening any popup window from Blender 3.0 (like Blender preferences or Render Image) when using latest up to date X11 in Manjaro with
libxcb 1.14 and libx11 1.7.3.1 (which already include "Fix poll_for_response race condition" from above gitlab link, so it seems 1 year old fix didn't fully help or something else broke in the meanwhile).

Current solution I found is to use Wayland instead of X11. With Wayland I never experienced the issue, with X11 I had crashes all the time.
Going back to donut tutorial now :).

I also had the exact same problem when opening any popup window from Blender 3.0 (like Blender preferences or Render Image) when using latest up to date X11 in Manjaro with libxcb 1.14 and libx11 1.7.3.1 (which already include "Fix poll_for_response race condition" from above gitlab link, so it seems 1 year old fix didn't fully help or something else broke in the meanwhile). Current solution I found is to use Wayland instead of X11. With Wayland I never experienced the issue, with X11 I had crashes all the time. Going back to donut tutorial now :).

Tadej Pečar commented

2022-01-12 15:19:30 +01:00

Added subscriber: @tpecar

Tadej Pečar commented

2022-01-12 15:19:30 +01:00

I'm also affected by this issue on Arch Linux with Blender 3.0.0, libx11 1.7.3.1-1 and libxcb 1.14-1.

I'm using KDE + i3 as the window manager (as per https://userbase.kde.org/Tutorials/Using_Other_Window_Managers_with_Plasma) under X11.

The main issue seems to be that when F12 is pressed, the default configuration is to open a new window, which also grabs focus and changes cursor location. It seems that some of these actions upset the X11 event handler and it aborts the application.

While this is not a Blender issue per-se, I assume that a workaround could be made on Blenders side to prevent the race condition.

My current workaround for now is to configure Blender to not open a new window, configured with Edit > Preferences > Interface > Editors > Temporary Editors > Render In : "Keep User Interface"

I'm also affected by this issue on Arch Linux with Blender 3.0.0, libx11 1.7.3.1-1 and libxcb 1.14-1. I'm using KDE + i3 as the window manager (as per https://userbase.kde.org/Tutorials/Using_Other_Window_Managers_with_Plasma) under X11. The main issue seems to be that when F12 is pressed, the default configuration is to open a new window, which also grabs focus and changes cursor location. It seems that some of these actions upset the X11 event handler and it aborts the application. While this is not a Blender issue per-se, I assume that a workaround could be made on Blenders side to prevent the race condition. My current workaround for now is to configure Blender to *not* open a new window, configured with Edit > Preferences > Interface > Editors > Temporary Editors > Render In : "Keep User Interface"

Harold commented

2022-01-19 22:36:50 +01:00

Added subscriber: @hhausman

Harold commented

2022-01-19 22:36:50 +01:00

Thanks as ever for blender, it's great. Very grateful for the impressive efforts of this community, always.

Got blender 3.0 today, first time using it on a newly built machine.

f12 reliably dumps core w/ this message:

[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
blender: ../../src/xcb_io.c:269: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
Aborted (core dumped)

Setup is vanilla ubuntu 21.10, though I also have installed and am using i3.

@tpecar suggests a workaround that works for me--- happy to provide more details or try anything else out to help devs reproduce/fix this issue.

Thanks as ever for blender, it's great. Very grateful for the impressive efforts of this community, always. Got blender 3.0 today, first time using it on a newly built machine. `f12` reliably dumps core w/ this message: ``` [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. blender: ../../src/xcb_io.c:269: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. Aborted (core dumped) ``` Setup is vanilla ubuntu 21.10, though I also have installed and am using `i3`. @tpecar suggests a workaround that works for me--- happy to provide more details or try anything else out to help devs reproduce/fix this issue.

Taschentuch commented

2022-02-17 23:50:22 +01:00

Added subscriber: @taschentuch

Taschentuch commented

2022-02-17 23:50:22 +01:00

Blender 3.0.1 (3.0.1+dfsg-7 from Debian sid): same error as above, "blender: ../../src/xcb_io.c:269: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.", after attempt to render via F12. Almost 100% sure crash, if moving around a light before pressing F12. Saving and reopening Blender before pressing F12, almost certain no crash (at least not in this scene). Also Intel gpu, i915.
Hope this helps anyhow.

Blender 3.0.1 (3.0.1+dfsg-7 from Debian sid): same error as above, "blender: ../../src/xcb_io.c:269: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.", after attempt to render via F12. Almost 100% sure crash, if moving around a light before pressing F12. Saving and reopening Blender before pressing F12, almost certain no crash (at least not in this scene). Also Intel gpu, i915. Hope this helps anyhow.

Harold commented

2022-02-17 23:57:42 +01:00

@taschentuch - very interesting. What window manager are you using?

Taschentuch commented

2022-02-18 00:35:55 +01:00

@hhausman : fluxbox

Omar Emara commented

2022-02-23 16:21:09 +01:00

Added subscriber: @OmarEmaraDev

Omar Emara commented

2022-02-23 16:21:09 +01:00

Looks like there is a patch to implement a workaround in XCB https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/113, seems to match the trace mentioned above.

Omar Emara commented

2022-03-24 08:35:01 +01:00

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

Omar Emara commented

2022-03-24 08:35:01 +01:00

It seems a fix was merged into LibX11. @intrr Can you retest with the latest mesa-git AUR package and see if that fixes the issue?

It seems a fix was merged into LibX11. @intrr Can you retest with the latest `mesa-git` AUR package and see if that fixes the issue?

Alexander Ewering commented

2022-03-25 16:23:55 +01:00

In #90247#1329025, @OmarEmaraDev wrote:
It seems a fix was merged into LibX11. @intrr Can you retest with the latest mesa-git AUR package and see if that fixes the issue?

Sorry, the Manjaro installation doesn't exist anymore. :(

> In #90247#1329025, @OmarEmaraDev wrote: > It seems a fix was merged into LibX11. @intrr Can you retest with the latest `mesa-git` AUR package and see if that fixes the issue? Sorry, the Manjaro installation doesn't exist anymore. :(

Omar Emara commented

2022-03-25 16:44:51 +01:00

@intrr Okay, no problem. Maybe another user can help with that. @blendear @tpecar @SpaceOne can any of you help test this?

Tadej Pečar commented

2022-03-26 11:20:44 +01:00

Ok, I have some time to kill, so I went ahead and checked if I can still reproduce the crash on the original system that exhibited this.

Note that the system (Thinkpad X230 with i5-3320M CPU @ 2.60GHz) hasn't been updated for some time and still has Blender 3.0.1 installed.

With the system as-is (Blender 3.0.1, i3 window manager), and Blender configured with "Temporary Editors > Render In > New Window", using a new General workspace (default cube) I can cause it to crash by hitting F12 (3-4 times, don't need to close the Render window between attempts) and moving the mouse within the window.

This happens regardless of the i3 window tiling configuration (crashes when Blender window either in tiled or tabbed configuration).

Providing version info for all dependencies, generated with

pactree -u blender | sort | while read -r pkg; do LANG=en_GB.UTF-8 LC_TIME=en_GB.UTF-8 pacman -Qi $pkg; done

blender-3.0.1-5-pactree-versions.txt

blender-3.0.1-5-pactree.txt

blender-3.0.1-5-crash-msg.txt

blender-3.0.1-5-mesa.txt

I'll update the system (possibly try with mesa-git as advised) and report the differences in the next post.

Ok, I have some time to kill, so I went ahead and checked if I can still reproduce the crash on the original system that exhibited this. Note that the system (Thinkpad X230 with i5-3320M CPU @ 2.60GHz) hasn't been updated for some time and still has Blender 3.0.1 installed. With the system as-is (Blender 3.0.1, i3 window manager), and Blender configured with "Temporary Editors > Render In > New Window", using a new General workspace (default cube) I can cause it to crash by hitting F12 (3-4 times, don't need to close the Render window between attempts) and moving the mouse within the window. This happens regardless of the i3 window tiling configuration (crashes when Blender window either in tiled or tabbed configuration). Providing version info for all dependencies, generated with ``` pactree -u blender | sort | while read -r pkg; do LANG=en_GB.UTF-8 LC_TIME=en_GB.UTF-8 pacman -Qi $pkg; done ``` [blender-3.0.1-5-pactree-versions.txt](https://archive.blender.org/developer/F12948053/blender-3.0.1-5-pactree-versions.txt) [blender-3.0.1-5-pactree.txt](https://archive.blender.org/developer/F12948052/blender-3.0.1-5-pactree.txt) [blender-3.0.1-5-crash-msg.txt](https://archive.blender.org/developer/F12948051/blender-3.0.1-5-crash-msg.txt) [blender-3.0.1-5-mesa.txt](https://archive.blender.org/developer/F12948050/blender-3.0.1-5-mesa.txt) I'll update the system (possibly try with mesa-git as advised) and report the differences in the next post.

Tadej Pečar commented

2022-03-26 12:16:27 +01:00

Ok, I've updated the system, Blender 3.1.0 with standard system packages still crashes.

Providing version info

blender-3.1.0-2-pactree-versions.txt

blender-3.1.0-pactree.txt

blender-3.1.0-2-mesa.txt

Will now try with mesa-git

Ok, I've updated the system, Blender 3.1.0 with standard system packages still crashes. Providing version info [blender-3.1.0-2-pactree-versions.txt](https://archive.blender.org/developer/F12948096/blender-3.1.0-2-pactree-versions.txt) [blender-3.1.0-pactree.txt](https://archive.blender.org/developer/F12948095/blender-3.1.0-pactree.txt) [blender-3.1.0-2-mesa.txt](https://archive.blender.org/developer/F12948094/blender-3.1.0-2-mesa.txt) Will now try with mesa-git

Tadej Pečar commented

2022-03-26 13:17:09 +01:00

Built mesa-git as-is, and Blender 3.1.0 still crashes.

Attaching build log and crash message.
mesa-git-build2.txt
blender-3.1.1-2-crash-msg-mesa.txt

At this point I would ask for assistance on how to proceed. I assume the fix was not included in this mesa-git build, isn't helping, or is provided by some other package?

(Note: blender-3.1.1-2-crash-msg-mesa.txt actually refers to Blender 3.1.0, there's a typo in the filename)

Built mesa-git as-is, and Blender 3.1.0 *still* crashes. Attaching build log and crash message. [mesa-git-build2.txt](https://archive.blender.org/developer/F12948155/mesa-git-build2.txt) [blender-3.1.1-2-crash-msg-mesa.txt](https://archive.blender.org/developer/F12948166/blender-3.1.1-2-crash-msg-mesa.txt) At this point I would ask for assistance on how to proceed. I assume the fix was not included in this mesa-git build, isn't helping, or is provided by some other package? (Note: blender-3.1.1-2-crash-msg-mesa.txt actually refers to Blender 3.1.0, there's a typo in the filename)

Omar Emara commented

2022-03-26 13:35:00 +01:00

@tpecar The fix is actually provided by the libx11-git package, which is a make dependency to mesa-git, but as far as I can tell from the log, that was not installed, so maybe my assumption is wrong and this needs to be done manually.
We mainly just want to test the mesa-git when linked against libx11-git, so if you can make sure its the former uses the latter during compilation, that would be the way to do.

@tpecar The fix is actually provided by the `libx11-git` package, which is a make dependency to `mesa-git`, but as far as I can tell from the log, that was not installed, so maybe my assumption is wrong and this needs to be done manually. We mainly just want to test the `mesa-git` when linked against `libx11-git`, so if you can make sure its the former uses the latter during compilation, that would be the way to do.

Tadej Pečar commented

2022-03-26 15:48:51 +01:00

Ok, I've installed libx11-git and rebuilt mesa-git, and yes, this had indeed fixed the issue!

Blender 3.1.0 is stable now when I try the procedures that had previously reliably invoked the xcb related crash.
I didn't check it for previous versions of Blender due to dependency issues, but I assume this would also fix it for previous versions, since it was a library issue.

For info, I've built both packages without any modifications / special flags. Given that these track development branches, the exact commits when I built the packages were

for libx11-git 8a368d80, which includes the 257927c5 fix
for mesa-git ae710f33

Now these changes still need to propagate into the standard prebuilt releases (of libx11, mesa), so I don't know if we should close the issue just yet, but otherwise we can consider it resolved.

Providing the build log
libx11-git-mesa-git-build.txt

Ok, I've installed `libx11-git` and rebuilt `mesa-git`, and yes, this had indeed fixed the issue! Blender 3.1.0 is stable now when I try the procedures that had previously reliably invoked the xcb related crash. I didn't check it for previous versions of Blender due to dependency issues, but I assume this would also fix it for previous versions, since it was a library issue. For info, I've built both packages without any modifications / special flags. Given that these track development branches, the exact commits when I built the packages were - for `libx11-git` [8a368d80](https:*gitlab.freedesktop.org/xorg/lib/libx11/-/tree/8a368d808fec166b5fb3dfe6312aab22c7ee20af), which includes the [257927c5](https:*gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/113) fix - for `mesa-git` [ae710f33](https://gitlab.freedesktop.org/mesa/mesa/-/tree/ae710f33296c5bf673fbe4b4c6a720d5552b4554) Now these changes still need to propagate into the standard prebuilt releases (of libx11, mesa), so I don't know if we should close the issue just yet, but otherwise we can consider it resolved. Providing the build log [libx11-git-mesa-git-build.txt](https://archive.blender.org/developer/F12948252/libx11-git-mesa-git-build.txt)

Omar Emara commented

2022-03-26 21:44:25 +01:00

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

Omar Emara closed this issue

2022-03-26 21:44:25 +01:00

Omar Emara commented

2022-03-26 21:44:25 +01:00

As we are not really aligned with releases of those libraries, we will just archive this issue for now, we can always reopen if the issue resurface.
@tpecar Thank you for your help!

As we are not really aligned with releases of those libraries, we will just archive this issue for now, we can always reopen if the issue resurface. @tpecar Thank you for your help!

Dennis commented

2022-05-04 16:43:12 +02:00

✅ For anyone looking for information about the resolution of this bug:

I can confirm that problem is solved after upgrading my system to Kubuntu 22.04 LTS without any additional steps (X11 / Mesa 22.0.1 / KDE).
Tested with Blender 3.0.1 installed from the default repository.

✅ **For anyone looking for information about the resolution of this bug:** I can confirm that problem is solved after upgrading my system to **Kubuntu 22.04 LTS** without any additional steps (X11 / Mesa 22.0.1 / KDE). Tested with **Blender 3.0.1** installed from the default repository.

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

Blender often crashes with xcb-related error messages #90247