Blender crashes when using the icon-based transforming tools #121118

New Issue

Martin · 2024-04-26T11:46:41+02:00

Martin commented

2024-04-26 11:46:41 +02:00

System Information
Operating system: Linux/Wayland
Graphics card: built-in Intel Corporation CometLake-U GT2 [UHD Graphics] (i915)

Blender Version
Broken: 4.1.1 (flatpak)
Worked: ?

Short description of error
When using the icon-based transformation tools (Move/Rotate/Scale) eventually blender will become unresponsive (crash).
Top reports blender to use 100% cpu usage (on one single cpu).

Exact steps for others to reproduce the error
Open blender, choose default startup General.
Move/Rotate/Scale the cube only using the icon-based tools (no keyboard shortscuts!) untill blender crashes. It may take a while, but will happen eventually.

**System Information** Operating system: Linux/Wayland Graphics card: built-in Intel Corporation CometLake-U GT2 [UHD Graphics] (i915) **Blender Version** Broken: 4.1.1 (flatpak) Worked: ? **Short description of error** When using the icon-based transformation tools (Move/Rotate/Scale) eventually blender will become unresponsive (crash). Top reports blender to use 100% cpu usage (on one single cpu). **Exact steps for others to reproduce the error** Open blender, choose default startup General. Move/Rotate/Scale the cube _only_ using the icon-based tools (no keyboard shortscuts!) untill blender crashes. It may take a while, but will happen eventually.

Martin added the

labels 2024-04-26 11:46:42 +02:00

Pratik Borhade commented

2024-04-26 11:53:10 +02:00

Broken: 4.1.1 (flatpak)

Hi, thanks for the report. Flatpack package of blender is not maintained by blender. Please report crash on their issue tracker.

> Broken: 4.1.1 (flatpak) Hi, thanks for the report. Flatpack package of blender is not maintained by blender. Please report crash on their issue tracker.

Pratik Borhade closed this issue

2024-04-26 11:53:14 +02:00

Blender Bot added

and removed

labels 2024-04-26 11:53:16 +02:00

Martin commented

2024-04-26 13:39:09 +02:00

Yeah ok, so I just crashed the official x64 binaries from blender.org for you.

Martin reopened this issue

2024-04-26 13:39:13 +02:00

Blender Bot added

and removed

labels 2024-04-26 13:39:15 +02:00

Iliya Katushenock commented

2024-04-26 13:41:48 +02:00

Maybe there is crash reason in blender, but if this is related with add-on, add-on developer should send more detailed report with necessary info. This still require cowling in how add-on work to be able to fix this.

Martin commented

2024-04-26 13:43:16 +02:00

Oh and this points to developer.blender.org, hence my assumption I was at the right address for flatpak bugreports, my apologies.

Oh and this points to developer.blender.org, hence my assumption I was at the right address for flatpak bugreports, my apologies. ![image](/attachments/97edba14-3727-4bcd-bbc8-106036992eda)

image.png

45 KiB

Martin commented

2024-04-26 13:54:05 +02:00

I just reproduced with (only) these add-ons enabled. What add-ons should I disable for a clean test?

I just reproduced with (only) these add-ons enabled. What add-ons should I disable for a clean test? ![image](/attachments/fcf1a14d-fe6a-42a8-88f8-9e20f72eb1a3)

image.png

39 KiB

Max Mustermann commented

2024-04-27 01:30:18 +02:00

How many edits would you say does it take to crash Blender? Also on the Flatpak version of 4.1.1 I have just made made over 200 icon based edits without Blender crashing.

I have made a lot of bug reports based on bugs I found in the Flatpak version (Of bugs that are not exclusive to the Flatpak version). Is this redirecting to a Flatpak issue tracker a new policy?

How many edits would you say does it take to crash Blender? Also on the Flatpak version of 4.1.1 I have just made made over 200 icon based edits without Blender crashing. I have made a lot of bug reports based on bugs I found in the Flatpak version (Of bugs that are not exclusive to the Flatpak version). Is this redirecting to a Flatpak issue tracker a new policy?

Martin commented

2024-04-27 10:09:20 +02:00

I don't count the number of edits, but if I 'hammer' Blender it crashes within 5 minutes. I do switch a lot between transformations and then do a lot of transformations per type.

Maybe it's a Wayland problem?

I don't count the number of edits, but if I 'hammer' Blender it crashes within 5 minutes. I do switch a lot between transformations and then do a lot of transformations per type. Maybe it's a Wayland problem?

Max Mustermann commented

2024-04-27 12:33:52 +02:00

I still can't reproduce it, also on Wayland. Do you have snapping turned on?

Martin commented

2024-04-27 19:14:20 +02:00

No, snapping is not turned on.

Martin commented

2024-04-27 23:51:20 +02:00

Here's a video illustrating the effect, for what it's worth...

blender_crash.mp4

10 MiB

Max Mustermann commented

2024-04-28 00:55:15 +02:00

Does Blender become unresponsive to inputs or does it close?

If it becomes unresponsive without closing, can you try switching the window focus to something else and back to Blender? Does that make Blender respond to inputs again?

Does Blender become unresponsive to inputs or does it close? If it becomes unresponsive without closing, can you try switching the window focus to something else and back to Blender? Does that make Blender respond to inputs again?

Max Mustermann commented

2024-04-28 01:10:57 +02:00

Check these out: #121094 #107642 #80458

Martin commented

2024-04-28 08:49:47 +02:00

No, I can't unfreeze it by switching focus and yes, this is Intel (mobile UHD) graphics and as said CPU usage goes to 100% (single thread).
--debug-gpu output until the freeze:

$ ./blender -d --debug-gpu
Switching to fully guarded memory allocator.
Blender 4.1.1
Build: 2024-04-15 23:47:45 Linux Release
argv[0] = ./blender
argv[1] = -d
argv[2] = --debug-gpu
Read prefs: "/home/martin/.config/blender/4.1/config/userpref.blend"
INFO (gpu.debug): Notification : Successfully hooked OpenGL debug callback using OpenGL 4.3
INFO (gpu.debug): Notification : Successfully hooked OpenGL debug callback using OpenGL 4.3

No, I can't unfreeze it by switching focus and yes, this is Intel (mobile UHD) graphics and as said CPU usage goes to 100% (single thread). --debug-gpu output until the freeze: ``` $ ./blender -d --debug-gpu Switching to fully guarded memory allocator. Blender 4.1.1 Build: 2024-04-15 23:47:45 Linux Release argv[0] = ./blender argv[1] = -d argv[2] = --debug-gpu Read prefs: "/home/martin/.config/blender/4.1/config/userpref.blend" INFO (gpu.debug): Notification : Successfully hooked OpenGL debug callback using OpenGL 4.3 INFO (gpu.debug): Notification : Successfully hooked OpenGL debug callback using OpenGL 4.3 ``` ![image](/attachments/b9db71d2-3dc5-4a24-8d1d-869ed11444da)

image.png

41 KiB

Pratik Borhade commented

2024-05-06 11:24:57 +02:00

Hi, this might be helpful, can you check:

$ echo 10000 | sudo tee /sys/class/drm/card0/engine/rcs0/preempt_timeout_ms
$ INTEL_DEBUG=reemit blender

Reference: #116322

Hi, this might be helpful, can you check: ``` $ echo 10000 | sudo tee /sys/class/drm/card0/engine/rcs0/preempt_timeout_ms $ INTEL_DEBUG=reemit blender ``` Reference: #116322

Pratik Borhade added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2024-05-06 11:25:11 +02:00

Sign in to join this conversation.