Blender randomly stops responding under Linux. #83939

Closed
opened 2020-12-18 21:11:28 +01:00 by Jakub Jaszewski · 13 comments

Blender randomly stops responding under Linux (Debian flavour - Buster and Bullseye versions respectively).
AMDGPU-PRO drivers installed manually - tested versions: 20.10 and 20.40.
2020-12-18_20-08.png
The issue happens during tasks such as: modeling, workspace switching, changing viewport shading, playing baked smoke simulation, rendering still images and animations.
There is no sign, warning or stuttering before hangup. The Blender process hangs with one or two CPU cores utilised. After killing the process with SIGTERM or SIGKILL options the process respawns and frees system resources.
Sometimes the RAM is not freed. The Blender and Blender Render windows never dissappears. They can be moved around, resized and switched between workspaces in Linux.

Broken with:
2.90.1 hash 3e85bb34d0
2.91.0 hash 0f45cab862
2.92.0 hash 010f44b855

There is no predictable way to reproduce it. I've attached dump from console with options

--debug-all --factory-startup

When the hangup happened the following lines appeared:

I1218 17:44:06.270004 65191 blender_session.cpp:586] Total render time: 15.4228
I1218 17:44:06.270020 65191 blender_session.cpp:587] Render time (without synchronization): 15.2074

Attaching full console log from the session:
blender_dump
system-info.txt

Blender randomly stops responding under Linux (Debian flavour - Buster and Bullseye versions respectively). AMDGPU-PRO drivers installed manually - tested versions: 20.10 and 20.40. ![2020-12-18_20-08.png](https://archive.blender.org/developer/F9516763/2020-12-18_20-08.png) The issue happens during tasks such as: modeling, workspace switching, changing viewport shading, playing baked smoke simulation, rendering still images and animations. There is no sign, warning or stuttering before hangup. The Blender process hangs with one or two CPU cores utilised. After killing the process with SIGTERM or SIGKILL options the process respawns and frees system resources. Sometimes the RAM is not freed. The Blender and Blender Render windows never dissappears. They can be moved around, resized and switched between workspaces in Linux. Broken with: 2.90.1 hash 3e85bb34d0d7 2.91.0 hash 0f45cab862b8 2.92.0 hash 010f44b855ca There is no predictable way to reproduce it. I've attached dump from console with options > --debug-all --factory-startup When the hangup happened the following lines appeared: ``` I1218 17:44:06.270004 65191 blender_session.cpp:586] Total render time: 15.4228 I1218 17:44:06.270020 65191 blender_session.cpp:587] Render time (without synchronization): 15.2074 ``` Attaching full console log from the session: [blender_dump](https://archive.blender.org/developer/F9516713/blender_dump) [system-info.txt](https://archive.blender.org/developer/F9516706/system-info.txt)

Added subscriber: @silex

Added subscriber: @silex

Added subscriber: @rjg

Added subscriber: @rjg

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

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

At a first glance I couldn't see anything in the log file that would explain the freeze. This could be a problem with the graphics driver. Unfortunately, we would need some reproducible steps that allows us to test and verify the problem on our systems.

At a first glance I couldn't see anything in the log file that would explain the freeze. This could be a problem with the graphics driver. Unfortunately, we would need some reproducible steps that allows us to test and verify the problem on our systems.

Thank you. I'll try to fiddle with drivers and find some solid information.

Thank you. I'll try to fiddle with drivers and find some solid information.

Added subscriber: @ankitm

Added subscriber: @ankitm

@ankitm suggested in DevTalk thread https://devtalk.blender.org/t/blender-randomly-hangs-what-cli-debug-options-should-be-enabled-for-gpu-issues/16660/3 running Blender with only one thread (-t 1 argument) to further troubleshoot.
I run animation render overnight that way and there's no sign of hangup so far, and Blender is still responsive.

@ankitm suggested in DevTalk thread https://devtalk.blender.org/t/blender-randomly-hangs-what-cli-debug-options-should-be-enabled-for-gpu-issues/16660/3 running Blender with only one thread (-t 1 argument) to further troubleshoot. I run animation render overnight that way and there's no sign of hangup so far, and Blender is still responsive.
Member

While reading the report I was (somehow) reminded of bb49aa0d69 and just threading in general so I suggested that -t 1 option.
If you can share a simple file with a few objects other people could test it on their systems too.

While reading the report I was (somehow) reminded of bb49aa0d69 and just threading in general so I suggested that -t 1 option. If you can share a simple file with a few objects other people could test it on their systems too.

A deadlock/livelock could certainly be a reason for a hang.

A deadlock/livelock could certainly be a reason for a hang.

Most of the hangups are happening in 2.90.1, as this is the version I'm running for production right now.
But it was released 23. Sep - way before multithreaded geometry export patch (21 Oct).
HANG_TEST_Blender_2.90.1.blend

As for locking - hangups are happening during intensive work.

Most of the hangups are happening in 2.90.1, as this is the version I'm running for production right now. But it was released 23. Sep - way before multithreaded geometry export patch (21 Oct). [HANG_TEST_Blender_2.90.1.blend](https://archive.blender.org/developer/F9518096/HANG_TEST_Blender_2.90.1.blend) As for locking - hangups are happening during intensive work.

After uninstalling AMDGPU-PRO drivers the hangups are gone. I've succesfully run animation render overnight and baked smoke simulation.

After uninstalling AMDGPU-PRO drivers the hangups are gone. I've succesfully run animation render overnight and baked smoke simulation.

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

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

@silex I'm closing the ticket then, as this seems to have been caused by an issue with the graphics driver.

@silex I'm closing the ticket then, as this seems to have been caused by an issue with the graphics driver.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#83939
No description provided.