Crash changing viewport shading mode while editing mesh #104242
Labels
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
7 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#104242
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: macOS-13.2-arm64-arm-64bit 64 Bits
Graphics card: Apple M1 Max Apple 4.1 Metal - 83
Blender Version
Broken: version: 3.4.1, branch: blender-v3.4-release, commit date: 2022-12-19 17:00, hash:
55485cb379
Short description of error
Get crash on random ways.
Seems to be linked to viewport render type in edit mode. I had the bug multiple times to confirm before sending it to you.
The crash seems to don't occur when the subdivision modifier is not visually activated. Proceed like it's described in the next part of the report.
I have also crashes randomly on the edit of the mesh while I'm using shortcut "GG" on multiple meshes but I don't know if it's linked.
I add the Apple report to you as apple-crash-report.txt file.
Exact steps for others to reproduce the error
crash.blend
apple-crash-report.txt
Thank you, have a nice day.
Added subscriber: @v4l3ntina
Crash changing shading mode / editing meshto Crash changing viewport shading mode while editing meshAdded subscriber: @PratikPB2123
Changed status from 'Needs Triage' to: 'Needs User Info'
Hi, thanks for the report. Does it crash in 3.5 with viewport metal backend?
Hi thank you for your feedback.
Yes I enabled METAL for both APPLE M1 MAX (GPU - 32 cores) & APPLE M1 MAX.
And did it crash?
Yes it is, I enabled this from the first install of Blender on this computer.
Added subscriber: @mano-wii
@mano-wii , can you replicate the crash in
M1
?Changed status from 'Needs User Info' to: 'Confirmed'
I can confirm the crash:
Happens in seemingly random places in Blender's code:
Also:
It doesn't happen with the
Metal
backend.Regression introduced in 3.4 between
c5feb4e6fe
(15 Aug ) and109cc14dba
(13 Sep)Added subscriber: @Michael-Parkin-White-Apple
Added subscriber: @Jeroen-Bakker
@mano-wii, what is not clear to me is if it is also reproducable in 3.5?
@Jeroen-Bakker, I have to check again. But it certainly is reproducible in 3.5 as I usually start testing from that one.
(The mention of the "introduced in 3.4 between
c5feb4e6fe
and109cc14dba
" is to facilitate the bisect that I can do later - or anyone else).I was able to reproduce this with the OpenGL backend in latest 3.5.0 branch, but not with the Metal backend. When debugging in OpenGL, the console reports Command buffer failures due to GPU hang:
Stack traces may not always correlate to the problem, as GPU work execution wont always be in sync with the host CPU side, if crash occurs immediately. Otherwise, crash will occur at the next GPU command flush.
As for the actual error, likely occurs if the firmware detects an infinite loop within a shader. Or possibly a circular resource dependency which deadlocks commands. (e.g. two passes submitted which end up being dependent on each other).
Best current guess is an issue with
OVERLAY_shader_wireframe
in OpenGL. Possible causes could be OOB buffer reads/misformatted vertex buffers etc;Any updates here? 3.5 enters Bcon4 (basically release candidate) in one week.
Can anyone confirm if this bug still exists in the latest daily 3.5 build?
https://builder.blender.org/download/daily/
It seems fixed for me there, testing with OpenGL backend on a Macbook Pro M1. It's been a month since the latest update and there have been a lot of fixes since. But I'm not able to reliably reproduce this so not sure. What I found:
11b16c4ae3b9
Also confirmed crash in 3.4.1 and no crash in 3.5
11b16c4ae3b9
on my Macbook Air M1 with macOS 13.0.0.So I will assume this is fixed unless some can still get it to crash.