Random System Freezes while using Blender #80073

Closed
opened 2020-08-24 12:16:33 +02:00 by Florian · 14 comments

Update

This seems to be a bug in the i915 graphics driver ... there is an open ticket over at their bug tracker: https://gitlab.freedesktop.org/drm/intel/-/issues/2380

System Information
Operating system: Arch Linux (current as of 2020-08-24)
Graphics card: Intel Integrated 10th Gen
system-info.txt: system-info.txt

Blender Version
Broken: (2.83.5, 2.91.0 alpha)
Worked: none

Graphical System Output is frozen system wide. Only fix able by restarting X or Wayland. Sometimes the last two frames flicker back and forth randomly.

Exact steps for others to reproduce the error
This happens randomly after a while after running a short Python script several times. Mostly while simply rotating the scene. I am using the Scripting Layout at that point.

Comment
Honestly I have no idea if this is even a blender problem ... but so far this has only manifested while running blender. As stated above I tried both X, Wayland and at least two versions of Blender. One of the builds had what I think was a cpu renderer option, which also crashed after a while. Is there a way to write debug output to a file that persists a reboot via console?

edit: Reproducable on:

  • Gnome (X, Classic and Wayland) and XFCE
  • X and Wayland
  • Two Blender Versions
  • i915 (intel driver) with and without "enable_guc=2" and "enable_fbc=1"

The only thing I can not rule out is that it's the Intel Graphics Driver ... but I can't really circumvent that one.

Python Script that was mentioned: script.py

**Update** This seems to be a bug in the i915 graphics driver ... there is an open ticket over at their bug tracker: https://gitlab.freedesktop.org/drm/intel/-/issues/2380 **System Information** Operating system: Arch Linux (current as of 2020-08-24) Graphics card: Intel Integrated 10th Gen system-info.txt: [system-info.txt](https://archive.blender.org/developer/F8808046/system-info.txt) **Blender Version** Broken: (2.83.5, 2.91.0 alpha) Worked: none Graphical System Output is frozen system wide. Only fix able by restarting X or Wayland. Sometimes the last two frames flicker back and forth randomly. **Exact steps for others to reproduce the error** This happens randomly after a while after running a short Python script several times. Mostly while simply rotating the scene. I am using the Scripting Layout at that point. **Comment** Honestly I have no idea if this is even a blender problem ... but so far this has only manifested while running blender. As stated above I tried both X, Wayland and at least two versions of Blender. One of the builds had what I think was a cpu renderer option, which also crashed after a while. Is there a way to write debug output to a file that persists a reboot via console? **edit:** Reproducable on: - Gnome (X, Classic and Wayland) and XFCE - X and Wayland - Two Blender Versions - i915 (intel driver) with and without "enable_guc=2" and "enable_fbc=1" The only thing I can not rule out is that it's the Intel Graphics Driver ... but I can't really circumvent that one. Python Script that was mentioned: [script.py](https://archive.blender.org/developer/F8808052/script.py)
Author

Added subscriber: @fho

Added subscriber: @fho
Author

This seems to be a bug in the i915 graphics driver ... there is an open ticket over at their bug tracker: https://gitlab.freedesktop.org/drm/intel/-/issues/2380

Not sure what an appropriate status for "not a blender problem" is.

This seems to be a bug in the i915 graphics driver ... there is an open ticket over at their bug tracker: https://gitlab.freedesktop.org/drm/intel/-/issues/2380 Not sure what an appropriate status for "not a blender problem" is.

Added subscriber: @iss

Added subscriber: @iss

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

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

Can you run Blender form console with --debug argument and redirect output to file just to see if we can confirm GPU/blender issue?

Can you run Blender form console with --debug argument and redirect output to file just to see if we can confirm GPU/blender issue?
Author

Sure. Here is the output of

blender --debug --debug-gpu

blender-log-2020-08-28T09:50+02:00.txt

Sure. Here is the output of ``` blender --debug --debug-gpu ``` [blender-log-2020-08-28T09:50+02:00.txt](https://archive.blender.org/developer/F8816810/blender-log-2020-08-28T09_50_02_00.txt)

I don't see any useful info in log. and script works in my case, but Perhaps I need correct data for it to fail. Could you also upload .blend file where you can run this script with crashing?
You could also try to simplify script to try to identify what causes crash by removing some operations.

I don't see any useful info in log. and script works in my case, but Perhaps I need correct data for it to fail. Could you also upload .blend file where you can run this script with crashing? You could also try to simplify script to try to identify what causes crash by removing some operations.
Author

I don't think it's related to the script ... I just included that for completeness. Actually I can crash blender without any file open and the other guy on the i915 bug tracker obviously does have a different scene.

I don't think it's related to the script ... I just included that for completeness. Actually I can crash blender without any file open and the other guy on the i915 bug tracker obviously does have a different scene.

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

Changed status from 'Needs User Info' to: 'Archived'
Richard Antalik self-assigned this 2020-08-28 13:20:30 +02:00

Thanks for information, I think we can safely assume this is not bug in Blender, so I will close this report. If you get more information, please leave a comment so we can reopen, or create new report with new relevant information.

Thanks for information, I think we can safely assume this is not bug in Blender, so I will close this report. If you get more information, please leave a comment so we can reopen, or create new report with new relevant information.

Added subscriber: @CepheidVariable

Added subscriber: @CepheidVariable

I apologize ahead of time for bothering you with this, but I wanted to point out that this is probably the same problem as https://developer.blender.org/T77466

I'm going to argue that it's a driver bug, because switching away from the Iris driver seems to resolve the crash, and the Intel gitlab discussion points to a geometry shader problem.

I bisected the commit that introduced the GPU hang on the Blender side, and it was commit d712f1f83a, which introduced a new shader for drawing smooth lines, using a geometry shader.

That said, Arch Linux's latest packaged version, 2.83.5-2, released on August 21st, seems to resolve the hang for me, so a commit somewhere between the 17th and the 21st might have fixed the cause of the GPU hang on Blender's side. I know it's not a driver fix that resolved it.

I apologize ahead of time for bothering you with this, but I wanted to point out that this is probably the same problem as https://developer.blender.org/T77466 I'm going to argue that it's a driver bug, because switching away from the Iris driver seems to resolve the crash, and the Intel gitlab discussion points to a geometry shader problem. I bisected the commit that introduced the GPU hang on the Blender side, and it was commit d712f1f83af881be536ec0d183b7d3025c172684, which introduced a new shader for drawing smooth lines, using a geometry shader. That said, Arch Linux's latest packaged version, 2.83.5-2, released on August 21st, seems to resolve the hang for me, so a commit somewhere between the 17th and the 21st might have fixed the cause of the GPU hang on Blender's side. I know it's not a driver fix that resolved it.

It does look like it is the same issue, when I read whole thread.

That said I will merge this report and keep that one open, since I am not sure if that could be considered a regression, or just a buggy driver.

It does look like it is the same issue, when I read whole thread. That said I will merge this report and keep that one open, since I am not sure if that could be considered a regression, or just a buggy driver.

Closed as duplicate of #77466

Closed as duplicate of #77466
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#80073
No description provided.