Maniphest T97256

Going into edit mode on the provided object crashes Blender
Closed, Archived

Assigned To
None
Authored By
Marko Grdinić (mrakgr)
Apr 11 2022, 9:00 PM
Tags
  • BF Blender
Subscribers
Hans Goudey (HooglyBoogly)
Marko Grdinić (mrakgr)
Philipp Oeser (lichtwerk)
Pratik Borhade (PratikPB2123)

Description

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: rBc77597cd0e15
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.

Related Objects

Event Timeline

Marko Grdinić (mrakgr) created this task.Apr 11 2022, 9:00 PM
Hans Goudey (HooglyBoogly) changed the task status from Needs Triage to Needs Information from User.Apr 11 2022, 9:13 PM
Hans Goudey (HooglyBoogly) added a subscriber: Hans Goudey (HooglyBoogly).

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?

Pratik Borhade (PratikPB2123) added subscribers: Philipp Oeser (lichtwerk), Pratik Borhade (PratikPB2123).Apr 12 2022, 5:36 AM

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!")

@Philipp Oeser (lichtwerk) had shared this script in T93972 :)

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.

Marko Grdinić (mrakgr) added a comment.Apr 12 2022, 10:32 AM

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.

Pratik Borhade (PratikPB2123) added a comment.Apr 12 2022, 2:54 PM

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

Philipp Oeser (lichtwerk) added a comment.Apr 12 2022, 3:08 PM

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)

Pratik Borhade (PratikPB2123) closed this task as Archived.Apr 12 2022, 3:13 PM

Ok, closing then.