Randomly crashes when clicking Blender by moving the mouse from another monitor under Linux. #110130

New Issue

Blender-King · 2023-07-15T08:16:36+02:00

Blender-King commented

2023-07-15 08:16:36 +02:00

System Information
Operating system: Linux 6.4.3, Gnome, Wayland, dual monitors with different scalings
Graphics card: Intel Arc A770

Blender Version
Broken: (example: 2.80, edbf15d3c0, master, 2018-11-28, as found on the splash screen) 3.6.0
Worked: (newest version of Blender that worked as expected) 3.5.0.

Short description of error
I have two monitors, A and B (main monitor). If I put Blender on B maximised, and keep clicking the empty desktop of monitor A (nothing on that monitor, so the desktop is showing) and Blender's empty viewport, in several tries, a white rectangle appears on Blender where I clicked as the top-left vertex, and then Blender crashes.

I don't know how to record multiple monitors at once in Linux (which is possible under Windows), so I just recorded the monitor where Blender was on. I am attaching the screen recording.

I ran Blender with blender --factory-startup --debug-all, the content of the blender.crash.txt was

# Blender 3.6.0, Commit date: 2023-06-27 08:08, Hash c7fc78b81ecb
bpy.ops.wm.splash()  # Operator
bpy.ops.wm.tool_set_by_id(name="builtin.select_box", cycle=False, space_type='VIEW_3D')  # Operator
bpy.ops.wm.tool_set_by_id(name="builtin.select_box", cycle=False, space_type='VIEW_3D')  # Operator
bpy.ops.wm.tool_set_by_id(name="builtin.select_box", cycle=False, space_type='VIEW_3D')  # Operator

# backtrace

# Python backtrace

The terminal output at crash was:

....

wm_event_do_handlers: Handling event
wmEvent type:1/LEFTMOUSE, val:1/PRESS, prev_type:1/LEFTMOUSE, prev_val:2/RELEASE, modifier={}, keymodifier:0, flag:{}, mouse:(503691,-307117), utf8:'', pointer:0x7fca17206160
UI_menutype_draw: opening menu "TOPBAR_MT_editor_menus"
UI_menutype_draw: opening menu "TIME_MT_editor_menus"
UI_menutype_draw: opening menu "VIEW3D_MT_editor_menus"
UI_menutype_draw: opening menu "VIEW3D_MT_editor_menus"

wm_event_do_handlers: Handling event
wmEvent type:1/LEFTMOUSE, val:2/RELEASE, prev_type:1/LEFTMOUSE, prev_val:1/PRESS, modifier={}, keymodifier:0, flag:{}, mouse:(1967,862), utf8:'', pointer:0x7fca17279000
Writing: /tmp/blender.crash.txt
Segmentation fault (core dumped)

Exact steps for others to reproduce the error

Find a Gnome PC with dual monitors with different scalings
Maximise Blender on one of the monitor.
Keep clicking two monitors in turn.

**System Information** Operating system: Linux 6.4.3, Gnome, Wayland, dual monitors with different scalings Graphics card: Intel Arc A770 **Blender Version** Broken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen) 3.6.0 Worked: (newest version of Blender that worked as expected) 3.5.0. ![image](/attachments/d359cd97-79bf-4936-82ff-4101373a5cea) **Short description of error** I have two monitors, A and B (main monitor). If I put Blender on B maximised, and keep clicking the empty desktop of monitor A (nothing on that monitor, so the desktop is showing) and Blender's empty viewport, in several tries, a white rectangle appears on Blender where I clicked as the top-left vertex, and then Blender crashes. I don't know how to record multiple monitors at once in Linux (which is possible under Windows), so I just recorded the monitor where Blender was on. I am attaching the screen recording. I ran Blender with `blender --factory-startup --debug-all`, the content of the blender.crash.txt was ``` # Blender 3.6.0, Commit date: 2023-06-27 08:08, Hash c7fc78b81ecb bpy.ops.wm.splash() # Operator bpy.ops.wm.tool_set_by_id(name="builtin.select_box", cycle=False, space_type='VIEW_3D') # Operator bpy.ops.wm.tool_set_by_id(name="builtin.select_box", cycle=False, space_type='VIEW_3D') # Operator bpy.ops.wm.tool_set_by_id(name="builtin.select_box", cycle=False, space_type='VIEW_3D') # Operator # backtrace # Python backtrace ``` The terminal output at crash was: ``` .... wm_event_do_handlers: Handling event wmEvent type:1/LEFTMOUSE, val:1/PRESS, prev_type:1/LEFTMOUSE, prev_val:2/RELEASE, modifier={}, keymodifier:0, flag:{}, mouse:(503691,-307117), utf8:'', pointer:0x7fca17206160 UI_menutype_draw: opening menu "TOPBAR_MT_editor_menus" UI_menutype_draw: opening menu "TIME_MT_editor_menus" UI_menutype_draw: opening menu "VIEW3D_MT_editor_menus" UI_menutype_draw: opening menu "VIEW3D_MT_editor_menus" wm_event_do_handlers: Handling event wmEvent type:1/LEFTMOUSE, val:2/RELEASE, prev_type:1/LEFTMOUSE, prev_val:1/PRESS, modifier={}, keymodifier:0, flag:{}, mouse:(1967,862), utf8:'', pointer:0x7fca17279000 Writing: /tmp/blender.crash.txt Segmentation fault (core dumped) ``` **Exact steps for others to reproduce the error** 1. Find a Gnome PC with dual monitors with different scalings 2. Maximise Blender on one of the monitor. 3. Keep clicking two monitors in turn.

screen.webm

2.6 MiB

image.png

43 KiB

Blender-King added the

labels 2023-07-15 08:16:36 +02:00

Blender-King changed title from ~~Randomly crashes when clicking Blender by moving the mouse from another monitor.~~ to Randomly crashes when clicking Blender by moving the mouse from another monitor under Linux.

2023-07-15 08:19:21 +02:00

Jesse Yurkovich commented

2023-07-15 08:26:22 +02:00

A similar wayland issue may have already been fixed. Can you try a 3.6.1 release candidate build and see if this still occurs: https://builder.blender.org/download/daily/

Jesse Yurkovich added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2023-07-15 08:26:33 +02:00

Blender-King commented

2023-07-15 08:40:01 +02:00

Seems like it's not happening with blender-3.6.1-candidate+v36.a8b82bd89e66-linux.x86_64-release.

Blender-King closed this issue

2023-07-15 08:40:04 +02:00