Crash trying to show an object by clicking the eye icon #88192
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#88192
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: Darwin-19.6.0-x86_64-i386-64bit 64 Bits
Graphics card: AMD Radeon Pro 580 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.19
Blender Version
Broken: version: 2.92.0, branch: master, commit date: 2021-02-24 16:25, hash:
02948a2cabWorked: (newest version of Blender that worked as expected)
Short description of error
Total and instant crash to desktop every time I click the eye to show "Leather Pants M". See screenshot.
Exact steps for others to reproduce the error
Click the eye to try showing "Leather Pants M".
Crashy Crash.blend.zip
Added subscriber: @Gillissie
I should have mentioned that the last version of Blender I used before 2.92 was 2.82, and didn't seem to have this issue. Strangely, it seems very specific to "Leather Pants M", since "Leather Pants F" works fine.
Added subscriber: @filedescriptor
Changed status from 'Needs Triage' to: 'Confirmed'
I can confirm this crash on the latest 3.0.0 Alpha. Will take a look.
It seems as though the mesh data got corrupted (specifically the edge data). Here is a short snippet of the debug output of
validate:Looks like something overwrote that data with garbage.
You can fix the mesh data by opening a "Python Console" editor in that file and entering the command:
D.meshes["Mesh.001"].validate().Now you should be able to unhide the object.
Changed status from 'Confirmed' to: 'Needs User Info'
@Gillissie Do you remember anything that you did or that happened, that could have caused this? Any small (also seemingly unrelated) detail could help. The tricky bit is knowing how the mesh data got into this state. Without that information we can't do much to prevent this from happening in the future and I will have to close the report.
Thanks, the python command did let me see the mesh.
I do a lot of work in this file, so I have no idea what particular thing may have caused it.
However, I would disagree with simply closing the report if you don't know what caused the data corruption. It's clear that regardless of how the data got corrupted, it caused a crash. You know how to fix the data so it doesn't crash. I suggest at the very least checking for whatever bad data could cause a crash and handling it gracefully instead of just crashing.
Changed status from 'Needs User Info' to: 'Archived'
Validating mesh data is an expensive operation. Doing it every time we try to access the data would result in extreme overhead. So that is not the solution.
In any case, we do not classify crashes due to corrupted meshes as bugs unless the user can reproduce the steps to get the mesh into that state. Closing.
How unfortunate. Validating may be expensive, but you only need to do it when preparing to show the mesh, not all the time.