Modeling context causes Blender to freeze with 100% CPU, even when set to GPU rendering #113096

New Issue

ben-little · 2023-10-01T00:31:45+02:00

ben-little commented

2023-10-01 00:31:45 +02:00

System Information
Operating system: Manjaro Linux (kernel 6.1.53-1)
Graphics card: Two separate cards: NVidia GeForce1080Ti and 1070

Blender Version
Broken: 3.6.2
Worked: Never

Short description of error

Blender crashes (UI freezes) and one CPU core goes to 100%.

Exact steps for others to reproduce the error

Simply use the modeling context (object mode, edit mode, maybe others). Moving vertices and using the "Move the view" tool seem more likely to cause it.

More Info

Even simple geometry (cube with 8 vertices) can cause it.

I have set the system preferences "Cycle Render Devices" to use CUDA. However nvidia-smi indicates that blender is not using either of my GPUs. I'm not sure if this is relevant because the problem occurs during modeling, not during render.

My guess is that this an infinite loop. It would be useful to understand which function call is causing the issue, but running blender --verbose 9 and blender --verbose debug aren't giving any output.

**System Information** Operating system: Manjaro Linux (kernel 6.1.53-1) Graphics card: Two separate cards: NVidia GeForce1080Ti and 1070 **Blender Version** Broken: 3.6.2 Worked: Never **Short description of error** Blender crashes (UI freezes) and one CPU core goes to 100%. **Exact steps for others to reproduce the error** Simply use the modeling context (object mode, edit mode, maybe others). Moving vertices and using the "Move the view" tool seem more likely to cause it. **More Info** Even simple geometry (cube with 8 vertices) can cause it. I have set the system preferences "Cycle Render Devices" to use CUDA. However `nvidia-smi` indicates that blender is not using either of my GPUs. I'm not sure if this is relevant because the problem occurs during modeling, not during render. My guess is that this an infinite loop. It would be useful to understand which function call is causing the issue, but running `blender --verbose 9` and `blender --verbose debug` aren't giving any output.

ben-little added the

labels 2023-10-01 00:31:46 +02:00

Pratik Borhade commented

2023-10-02 06:30:23 +02:00

Hi, thanks for the report. Does it happen with simple objects? Try factory reset in case an add-on is interfering: File > Defaults > Load Factory Settings

However nvidia-smi indicates that blender is not using either of my GPUs.

Print system info to find out which GPU is used: Help > Save System Info
Also check memory utilization to figure this out.

Hi, thanks for the report. Does it happen with simple objects? Try factory reset in case an add-on is interfering: `File > Defaults > Load Factory Settings` > However nvidia-smi indicates that blender is not using either of my GPUs. Print system info to find out which GPU is used: `Help > Save System Info` Also check memory utilization to figure this out.

Pratik Borhade added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2023-10-02 06:30:32 +02:00

ben-little commented

2023-10-03 18:43:32 +02:00

Does it happen with simple objects?

Yes, it happens with the default file (cube with 8 vertices).

Try factory reset in case an add-on is interfering

I have not manually installed any add-ons. I am a first-time blender user.

Print system info to find out which GPU is used

Looks like it's using the CPU:

GPU:
====================================

renderer:	'Mesa Intel(R) UHD Graphics 630 (CFL GT2)'
vendor:		'Intel'
version:	'4.6 (Core Profile) Mesa 23.1.7-1'
device type:	'INTEL'
backend type:	'OPENGL'
extensions:
...

Also check memory utilization to figure this out

Memory use is negligible according to top:

PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND                                                         
161182 ben       20   0   10.4g 563864 271668 R 100.0   1.7   0:48.78 blender

I ran gdb on it and did a backtrace during the freeze. Not sure if this helps. Looks like an ioctl call where it's getting stuck, which could be anything based on my limited understanding of ioctl.

0x00007fffe530c9df in ioctl () from /usr/lib/libc.so.6
(gdb) bt
#0  0x00007fffe530c9df in ioctl () at /usr/lib/libc.so.6
#1  0x00007fffafdda2a0 in  () at /usr/lib/dri/iris_dri.so
#2  0x00007fffaf5f9f2c in  () at /usr/lib/dri/iris_dri.so
#3  0x00007fffaf3aac9e in  () at /usr/lib/dri/iris_dri.so
#4  0x00007fffaf3ab334 in  () at /usr/lib/dri/iris_dri.so
#5  0x00007fffaf3ab484 in  () at /usr/lib/dri/iris_dri.so
#6  0x0000555558a7b07c in  ()
#7  0x00005555589ed6c1 in  ()
#8  0x00005555589ec445 in  ()
#9  0x00005555564b669f in  ()
#10 0x00005555564b7351 in  ()
#11 0x000055555648d482 in  ()
#12 0x000055555648dbfd in  ()
#13 0x000055555648ea69 in  ()
#14 0x00005555564818b0 in  ()
#15 0x0000555555d90441 in  ()
#16 0x00007fffe5227cd0 in  () at /usr/lib/libc.so.6
#17 0x00007fffe5227d8a in __libc_start_main () at /usr/lib/libc.so.6
#18 0x0000555555db3965 in  ()

> Does it happen with simple objects? Yes, it happens with the default file (cube with 8 vertices). > Try factory reset in case an add-on is interfering I have not manually installed any add-ons. I am a first-time blender user. > Print system info to find out which GPU is used Looks like it's using the CPU: ``` GPU: ==================================== renderer: 'Mesa Intel(R) UHD Graphics 630 (CFL GT2)' vendor: 'Intel' version: '4.6 (Core Profile) Mesa 23.1.7-1' device type: 'INTEL' backend type: 'OPENGL' extensions: ... ``` > Also check memory utilization to figure this out Memory use is negligible according to `top`: ``` PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 161182 ben 20 0 10.4g 563864 271668 R 100.0 1.7 0:48.78 blender ``` --- I ran `gdb` on it and did a backtrace during the freeze. Not sure if this helps. Looks like an ioctl call where it's getting stuck, which could be anything based on my limited understanding of ioctl. ``` 0x00007fffe530c9df in ioctl () from /usr/lib/libc.so.6 (gdb) bt #0 0x00007fffe530c9df in ioctl () at /usr/lib/libc.so.6 #1 0x00007fffafdda2a0 in () at /usr/lib/dri/iris_dri.so #2 0x00007fffaf5f9f2c in () at /usr/lib/dri/iris_dri.so #3 0x00007fffaf3aac9e in () at /usr/lib/dri/iris_dri.so #4 0x00007fffaf3ab334 in () at /usr/lib/dri/iris_dri.so #5 0x00007fffaf3ab484 in () at /usr/lib/dri/iris_dri.so #6 0x0000555558a7b07c in () #7 0x00005555589ed6c1 in () #8 0x00005555589ec445 in () #9 0x00005555564b669f in () #10 0x00005555564b7351 in () #11 0x000055555648d482 in () #12 0x000055555648dbfd in () #13 0x000055555648ea69 in () #14 0x00005555564818b0 in () #15 0x0000555555d90441 in () #16 0x00007fffe5227cd0 in () at /usr/lib/libc.so.6 #17 0x00007fffe5227d8a in __libc_start_main () at /usr/lib/libc.so.6 #18 0x0000555555db3965 in () ```

Pratik Borhade added

Status

Needs Triage

and removed

Status

Needs Information from User

labels 2023-10-04 11:35:05 +02:00

Richard Antalik commented

2023-10-10 22:19:03 +02:00

I assume this is same issue as #80458, #108875, #112880, and maybe #107642. Probably only solution is to configure your X server to use one of your dedicated GPUs

Will close as duplicate.

I assume this is same issue as #80458, #108875, #112880, and maybe #107642. Probably only solution is to configure your X server to use one of your dedicated GPUs Will close as duplicate.

Richard Antalik closed this issue

2023-10-10 22:19:05 +02:00

Blender Bot added

and removed

labels 2023-10-10 22:19:08 +02:00

ben-little commented

2023-10-15 03:12:21 +02:00

As suggested by the reporter of #112880, I checked the system journal with journalctl | grep -i blender and got

kernel: i915 0000:00:02.0: [drm] blender[9692] context reset due to GPU hang
kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:85df9e9f, in blender [9692]

So this is a likely a duplicate of that issue, which seems to be caused by a known bug in i915 firmware. https://gitlab.freedesktop.org/drm/intel/-/issues/2024

As suggested by the reporter of #112880, I checked the system journal with `journalctl | grep -i blender` and got ``` kernel: i915 0000:00:02.0: [drm] blender[9692] context reset due to GPU hang kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:85df9e9f, in blender [9692] ``` So this is a likely a duplicate of that issue, which seems to be caused by a known bug in i915 firmware. https://gitlab.freedesktop.org/drm/intel/-/issues/2024

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

Modeling context causes Blender to freeze with 100% CPU, even when set to GPU rendering #113096