Page MenuHome
Create Task
Maniphest T81514

Blender crashed and now when I try to open that file still crash
Closed, ArchivedPublicBUG
Actions

Description

System Information
Mac book pro 16"
Operating system: Mac os catalina 10.15.6
Graphics card:AMD Radeon Pro 5500M 8 GB / Intel UHD Graphics 630 1536 MB

Blender Version
Broken: 2.90.0 (2.90.0 2020-08-31)

Short description of error
I was duplicating two object with just few circles edge and move it to a collection, blender crash and reopen that file crash blender every time, I've tried also with 2.79 blender version, same problem, unfortunaly I've tried to restart my mac for try to fix that but now I can't see any autosave file. Laso the automatic backup .blend1 crash.

Exact steps for others to reproduce the error
Shift + D for duplicate two objects and press M to move to collection, blender crash, try to reopen the file blender crash, try to open backup .blend1 still crash.

Crashed file:crash-blender29

Related Objects

Mentioned Here
T2: Wrong licenses

Event Timeline

Jean claude Chiementin (GGKMNTN) created this task.Oct 7 2020, 5:30 PM
Jean claude Chiementin (GGKMNTN) updated the task description. (Show Details)Oct 7 2020, 8:27 PM
Hans Goudey (HooglyBoogly) changed the task status from Needs Triage to Needs Information from User.Oct 7 2020, 9:07 PM
Hans Goudey (HooglyBoogly) added a subscriber: Hans Goudey (HooglyBoogly).

Thanks for the report. Your file is 1GB in size though, do you mind providing a smaller file with the same error?

Jean claude Chiementin (GGKMNTN) added a comment.Oct 7 2020, 9:48 PM

Ok I've tried to append nly the last objects created today on a new file:
crash report file light

If you open it and switch from scene to scene.001 it crash, I hope it crash for the same bug on the original file.

For my original problem I fixed it by append on a two days old backup file only the object sthat I created these last days and it seems stable.

Hans Goudey (HooglyBoogly) changed the task status from Needs Information from User to Confirmed.EditedOct 7 2020, 10:35 PM
Hans Goudey (HooglyBoogly) added a project: Modeling.

Okay, I can confirm that switching the scene causes Blender to crash, in 2.91 too. Validating the mesh that causes the crash reveals that it has invalid geometry though:

D.meshes['Cylinder.033'].validate(verbose=True)
#~ True
#~

I'm not sure how we triage reports with invalid geometry. It depends how it was created I guess. Any idea how you created the mesh (not object) "Cylinder.033"?

Jean claude Chiementin (GGKMNTN) added a comment.Oct 7 2020, 10:51 PM

I Was duplicate two similiar objects, two inset circle that I've obtain by duplicate and separate a loop edge from another object. So from an original object created by a cylinder, I have selected a loop edge, a circle, then I have duplicate this and scale it. Both of these last object had an array for repeat it radially 5 times. Then I have duplicate this last two objects and when I've tried to move them in a collection Blender crashed, I don't know if the problem is caused by duplicate these two last objects (the originals was already there since I duplicated-separate them from the original cylinder) or when I've tried to move to a collection, because I did these two operations almost at thew same time using shortcuts. I hope my description is enough clear and I hope it can be usefull, thanks for your support!

Bastien Montagne (mont29) changed the task status from Confirmed to Needs Information from User.Oct 13 2020, 2:37 PM
Bastien Montagne (mont29) changed the subtype of this task from "Report" to "Bug".
Bastien Montagne (mont29) added a subscriber: Bastien Montagne (mont29).

We need a consistent precise way to reproduce that mesh corruption, otherwise we cannot investigate the issue, let alone fix it.

Jean claude Chiementin (GGKMNTN) added a comment.Oct 13 2020, 2:44 PM

I wrote all I did before it crashed, tell me what can I do for help you.

Bastien Montagne (mont29) added a comment.Oct 13 2020, 9:22 PM

@Jean claude Chiementin (GGKMNTN) the problem is that if it only happens once, then we cannot do anything about it, we need to be able to reproduce the bug. Otherwise it just a 'glitch'...

So we do not need to know what you were doing when the problem happened, but what to do to make it happen again

Bastien Montagne (mont29) closed this task as Archived.Oct 20 2020, 2:43 PM
Bastien Montagne (mont29) claimed this task.

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

Thanks again for the report. If the problem persists please open a new report with the required information.