Crash on undo or deleting an armature #40998

New Issue

Yousef Harfoush · 2014-07-09T03:17:51+02:00

Yousef Harfoush commented

2014-07-09 03:17:51 +02:00

System Information
windows 8.1 x64, geforce 660

Blender Version
Broken: since 2.70
Worked: 2.69

Short description of error
Crash on undo or deleting an armature

Exact steps for others to reproduce the error
in the armature in the attached file, try to delete it, or move in pose mode and undo, it will crash.

compiled using scons and mingw, also tested msvc2013

the file:
ep1_err.blend

**System Information** windows 8.1 x64, geforce 660 **Blender Version** Broken: since 2.70 Worked: 2.69 **Short description of error** Crash on undo or deleting an armature **Exact steps for others to reproduce the error** in the armature in the attached file, try to delete it, or move in pose mode and undo, it will crash. compiled using scons and mingw, also tested msvc2013 the file: [ep1_err.blend](https://archive.blender.org/developer/F97135/ep1_err.blend)

Yousef Harfoush commented

2014-07-09 03:17:51 +02:00

Changed status to: 'Open'

Yousef Harfoush commented

2014-07-09 03:17:51 +02:00

Added subscriber: @bat3a

Sergey Sharybin commented

2014-07-09 09:35:15 +02:00

Added subscriber: @Sergey

Sergey Sharybin commented

2014-07-09 10:03:01 +02:00

This is actually a corrupted file. It worked before because of some specifics of old memory allocator we used. The same behavior you'll have running blender with --debug-memory command line argument.

But the root of the issue comes to the fact that your object has an unknown type of constraint. You can see it by running this in the python console: C.object.constraints[0]

In order to fix the issue we need to know how exactly to reproduce such a situation from scratch.

This is actually a corrupted file. It worked before because of some specifics of old memory allocator we used. The same behavior you'll have running blender with --debug-memory command line argument. But the root of the issue comes to the fact that your object has an unknown type of constraint. You can see it by running this in the python console: C.object.constraints[0] In order to fix the issue we need to know how exactly to reproduce such a situation from scratch.

Yousef Harfoush commented

2014-07-09 23:29:40 +02:00

In order to fix the issue we need to know how exactly to reproduce such a situation from scratch.

it's a simple armature with ik constraint nothing more, made in 2.5x series, and there are no error in 2.69 and works as expected, if the file is corrupt i imported the rig in an new file, and had the same error after v.2.69, does this help?

is there anything i can help with?

thank you.

``` In order to fix the issue we need to know how exactly to reproduce such a situation from scratch. ``` it's a simple armature with ik constraint nothing more, made in 2.5x series, and there are no error in 2.69 and works as expected, if the file is corrupt i imported the rig in an new file, and had the same error after v.2.69, does this help? is there anything i can help with? thank you.

Sergey Sharybin commented

2014-07-09 23:44:15 +02:00

No, it does not help. As said -- we need to know how to reproduce such a corrupted file from a file which is NOT corrupted. We can't do anything about this file really.

Blender 2.69 worked because it used different memory allocator, which is now available if you use --debug-memory command line argument. Blender 2.69 just silently ignored the whole bunch of errors in this case, you can see all of them if you open the console. This was changed in order to make memory allocator much more friendly for threading (as a part of threaded depsgraph project).

So in order to solve the actual issue we need to fix a bug which allowed you to corrupt constraints stack, but for this we really do need to know how to produce such situation from scratch (or at least non-corrupted file).

No, it does not help. As said -- we need to know how to reproduce such a corrupted file from a file which is NOT corrupted. We can't do anything about this file really. Blender 2.69 worked because it used different memory allocator, which is now available if you use `--debug-memory` command line argument. Blender 2.69 just silently ignored the whole bunch of errors in this case, you can see all of them if you open the console. This was changed in order to make memory allocator much more friendly for threading (as a part of threaded depsgraph project). So in order to solve the actual issue we need to fix a bug which allowed you to corrupt constraints stack, but for this we really do need to know how to produce such situation from scratch (or at least non-corrupted file).

Yousef Harfoush commented

2014-07-10 00:00:52 +02:00

so importing the old file in a new file doesn't solve the corruption, then do you recommend anything to rescue my file?

thank you.

so importing the old file in a new file doesn't solve the corruption, then do you recommend anything to rescue my file? thank you.

Sergey Sharybin commented

2014-07-10 00:12:06 +02:00

Changed status from 'Open' to: 'Archived'

Sergey Sharybin closed this issue

2014-07-10 00:12:06 +02:00

Sergey Sharybin self-assigned this 2014-07-10 00:12:06 +02:00

Sergey Sharybin commented

2014-07-10 00:12:06 +02:00

Go to 2.69, add a new armature with single bone, go object data buttons, change armature datablock from Armature to afkar.Arm.001, delete old armature, save. File should work fine in new blender as well.

You would probably want to copy-paste pose as well.

This is all rather workaround, as said -- real fix could only be done when we know for sure how to produce such a file. For until then i'm gonna to archive the report.

Go to 2.69, add a new armature with single bone, go object data buttons, change armature datablock from Armature to afkar.Arm.001, delete old armature, save. File should work fine in new blender as well. You would probably want to copy-paste pose as well. This is all rather workaround, as said -- real fix could only be done when we know for sure how to produce such a file. For until then i'm gonna to archive the report.

Yousef Harfoush commented

2014-07-11 04:45:56 +02:00

that worked.

thanks

that worked. thanks

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Crash on undo or deleting an armature #40998