Going into edit mode on the provided object crashes Blender #97256

Closed
opened 2022-04-11 21:00:24 +02:00 by Marko Grdinić · 11 comments

System Information
Operating system: Windows-10-10.0.19044-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.96

Blender Version
Broken: version: 3.1.0, branch: master, commit date: 2022-03-08 18:16, hash: c77597cd0e
Worked: (newest version of Blender that worked as expected)

Short description of error
When I try tabbing into edit mode on the object, Blender crashes. I don't know how I managed to corrupt it.

Exact steps for others to reproduce the error
Tab the object.

Bug.blend

**System Information** Operating system: Windows-10-10.0.19044-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.96 **Blender Version** Broken: version: 3.1.0, branch: master, commit date: 2022-03-08 18:16, hash: `c77597cd0e` Worked: (newest version of Blender that worked as expected) **Short description of error** When I try tabbing into edit mode on the object, Blender crashes. I don't know how I managed to corrupt it. **Exact steps for others to reproduce the error** Tab the object. [Bug.blend](https://archive.blender.org/developer/F12996429/Bug.blend)
Author

Added subscriber: @mrakgr

Added subscriber: @mrakgr
Member

Added subscriber: @HooglyBoogly

Added subscriber: @HooglyBoogly
Member

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

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

Hi, I can confirm the crash. The reason for the crash is that the mesh has stored that vertex 1372509248 is selected, but there are only 8 vertices.

What is the history of this file? Can this be reproduced?

Hi, I can confirm the crash. The reason for the crash is that the mesh has stored that vertex 1372509248 is selected, but there are only 8 vertices. What is the history of this file? Can this be reproduced?
Member

Added subscribers: @lichtwerk, @PratikPB2123

Added subscribers: @lichtwerk, @PratikPB2123
Member

Yes mesh is corrupted.
Execute the following script, It'll detect the mesh corruption and will also fix the mesh

for obj in bpy.data.objects:

if obj.type == "MESH" and obj.data is not None:
if obj.data.validate():
print(f"Error found: object {obj.name} had invalid mesh data!")```

@lichtwerk had shared this script in #93972 :)
> I don't know how I managed to corrupt it.

Unfortunately unless there are clear instructions on how to reproduce it from scratch we cannot debug this any further.
Things that may cause mesh corruption: Importers, development versions of Blender, modeling tools.
Yes mesh is corrupted. Execute the following script, It'll detect the mesh corruption and will also fix the mesh ```import bpy for obj in bpy.data.objects: ``` if obj.type == "MESH" and obj.data is not None: if obj.data.validate(): print(f"Error found: object {obj.name} had invalid mesh data!")``` ``` @lichtwerk had shared this script in #93972 :) > I don't know how I managed to corrupt it. Unfortunately unless there are clear instructions on how to reproduce it from scratch we cannot debug this any further. Things that may cause mesh corruption: Importers, development versions of Blender, modeling tools.
Author

Unfortunately unless there are clear instructions on how to reproduce it from scratch we cannot debug this any further.

This is going to be hard. During that session I was working on a desk and playing around with modifiers and only realized the object was corrupted much later. I wasn't really doing anything esoteric, for the specific object I was only using subdiv and maybe decimate and triangulate. Apart from that, there is no way I can remember the specific sequence of action. The culprit might not be the modifier. There might also be a chance that me working on another object in the scene might have done something. I was hoping the save file might give enough of a clue, but nevermind it for now. I'll keep an eye open in the future in case I run into the bug again. Please feel free to close this.

> Unfortunately unless there are clear instructions on how to reproduce it from scratch we cannot debug this any further. This is going to be hard. During that session I was working on a desk and playing around with modifiers and only realized the object was corrupted much later. I wasn't really doing anything esoteric, for the specific object I was only using subdiv and maybe decimate and triangulate. Apart from that, there is no way I can remember the specific sequence of action. The culprit might not be the modifier. There might also be a chance that me working on another object in the scene might have done something. I was hoping the save file might give enough of a clue, but nevermind it for now. I'll keep an eye open in the future in case I run into the bug again. Please feel free to close this.
Member

Hi, thanks for the information.
I think we can close this report if source of the mesh corruption is not known to us.
@lichtwerk & @HooglyBoogly , thoughts?

Hi, thanks for the information. I think we can close this report if source of the mesh corruption is not known to us. @lichtwerk & @HooglyBoogly , thoughts?
Member

If we have no way to reproduce, we usually close the report, yes!
(we can always reopen in case these repro steps are found later)

If we have no way to reproduce, we usually close the report, yes! (we can always reopen in case these repro steps are found later)
Member

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

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

Ok, closing then.

Ok, closing then.
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
4 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#97256
No description provided.