Page MenuHome

Blender GPU Render crashes with NVidia in Ubuntu
Closed, ResolvedPublic

Description

System Information
Operating system: Linux LX-XPS 5.15.0-48-generic #54-Ubuntu SMP Fri Aug 26 13:26:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Graphics card: NVIDIA GM107M [GeForce GTX 960M] / HD Graphics 530

Blender Version
Broken: version: 3.3.0, branch: master, commit date: 2022-09-06 15:39, hash: 0759f671ce1f, type: release build date: 2022-09-07, 00:16:43
Worked: None

Short description of error
Starting blender by default, showing only the sample cube in the initial viewport :

  • In "Preferences-> System -> Cycles Render Devices -> CUDA" : "Nvidia GeForce GTX960" is selected
  • In "Select Viewport Shading": select "Rendered in Viewport Shading" with "Scene Lights" ans "Scene Words" boxes checked.
  • In the render Properties Menu select "Cycles as Render Engine"
  • Select "GPU Compute" as Device
  • Blender closes automatically.

Using "Eevee" or "Cycles as Render Engine" with "CPU as Device", work correctly.

Event Timeline

Richard Antalik (ISS) changed the task status from Needs Triage to Needs Information from User.Sep 29 2022, 9:30 PM

I think, that @Philipp Oeser (lichtwerk) has similar GPU and runs Linux. I am not able to reproduce here.

Please and run blender from console with -d argument, upload output and /tmp/blender.crash.txt file if one is created. Also check if this happens with alpha build from https://builder.blender.org/download/daily/

Cannot repro here (both on my 970m and 3080m)

Crash logs might help.

HI! Thanks for the answer! the result of executing blender -d is:

Switching to fully guarded memory allocator.
Blender 3.3.0
Build: 2022-09-07 00:16:43 Linux release
argv[0] = ./blender
argv[1] = -d
Read prefs: /home/olisseh/.config/blender/3.3/config/userpref.blend
Writing: /tmp/blender.crash.txt
Fallo de segmento (rexistráronse os datos da memoria)

And the crash log (/tmp/blender.crash.txt):

# Blender 3.3.0, Commit date: 2022-09-06 15:39, Hash 0759f671ce1f
bpy.context.space_data.shading.type = 'RENDERED'  # Property
bpy.context.space_data.context = 'RENDER'  # Property
bpy.context.scene.render.engine = 'CYCLES'  # Property
bpy.context.scene.cycles.device = 'GPU'  # Property

# backtrace
./blender() [0xbdfaf60]
./blender() [0x8de26a]
/lib/x86_64-linux-gnu/libc.so.6(+0x42520) [0x7f999236b520]
/lib64/ld-linux-x86-64.so.2(+0x324d) [0x7f999286024d]
/lib/x86_64-linux-gnu/libc.so.6(_dl_catch_exception+0x88) [0x7f999249dc28]
/lib/x86_64-linux-gnu/libc.so.6(_dl_catch_error+0x33) [0x7f999249dcf3]
/lib/x86_64-linux-gnu/libc.so.6(+0x901ae) [0x7f99923b91ae]
/lib/x86_64-linux-gnu/libc.so.6(dlclose+0x28) [0x7f99923b8ed8]
/lib/x86_64-linux-gnu/libcuda.so(+0x218011) [0x7f99581b3011]
/lib/x86_64-linux-gnu/libcuda.so(+0x2f4a57) [0x7f995828fa57]
./blender() [0x27b3ae1]
./blender() [0x31ce0c2]
./blender() [0x31ce5d3]
./blender() [0x31c3fdd]
./blender() [0x31c507c]
./blender() [0x31c5118]
./blender() [0x3132727]
./blender() [0x3133132]
./blender() [0x3133417]
./blender() [0x824c6be]
./blender() [0xc28db30]
/lib/x86_64-linux-gnu/libc.so.6(+0x94b43) [0x7f99923bdb43]
/lib/x86_64-linux-gnu/libc.so.6(+0x126a00) [0x7f999244fa00]

# Python backtrace

If i could help in any other way, please let me know.

Thanks in advance!

Seems that binary is stripped, so we can't see where the crash occurred. Can you re-check and upload logs with build from builder.blender.org/?

@Richard Antalik (ISS)

Hi, i,ve just download Blender 3.4.0 Alpha and try to execute the same way i've described in my first post. The resutl of executing blender -d is:

(base)~/Apps/blender-3.4$ ./blender -d
Switching to fully guarded memory allocator.
Blender 3.4.0 Alpha
Build: 2022-10-04 01:07:10 Linux release
argv[0] = ./blender
argv[1] = -d
Writing userprefs: '/home/olisseh/.config/blender/3.4/config/userpref.blend' ok
Info: Preferences saved

Writing: /tmp/blender.crash.txt
Fallo de segmento (rexistráronse os datos da memoria)
(Memory dumped) Segment fault (free translate)

And the crash log (/tmp/blender.crash.txt):

# Blender 3.4.0, Commit date: 2022-10-04 00:19, Hash 22c3db72ca2f
Preferences saved  # Info
bpy.context.space_data.shading.type = 'RENDERED'  # Property
bpy.context.space_data.shading.type = 'RENDERED'  # Property
bpy.context.space_data.context = 'RENDER'  # Property
bpy.context.scene.render.engine = 'CYCLES'  # Property
bpy.context.scene.cycles.device = 'GPU'  # Property

# backtrace

# Python backtrace

Original blender.crash.txt gone attached. If you would need any other logfile, please, let me know.

Thanks!!!

Philipp Oeser (lichtwerk) changed the task status from Needs Information from User to Needs Triage.Nov 4 2022, 2:09 PM
Richard Antalik (ISS) changed the task status from Needs Triage to Needs Information from User.Nov 7 2022, 7:11 PM

Sorry, I have missed notification on this report, I still don't see backtrace in crash report, so I would assume this crashed somewhere in CUDA backend. Previous backtrace seems to support this assumption. So I think, that only solution would be to update GPU drivers, since others don't seem to have this issue.

Can you click on Help > Save System Info and upload saved file?

Hi! I've try to update (again) the GPU driver v510, and it works... now Blender is rendering using cycles with GPU.

Thanks to all for helping! :-)

olisseh (olisseh) closed this task as Resolved.Nov 9 2022, 9:13 AM
olisseh (olisseh) claimed this task.