Rigify crash when when I press "Generate" #42593

New Issue

Jefferson Rausseo · 2014-11-13T23:01:11+01:00

Jefferson Rausseo commented

2014-11-13 23:01:11 +01:00

System Information
Ubuntu 14.04
Nvidia 8600gt

Blender Version
Broken: 2.72 3967d1c (compile with scons)

Short description of error
When I add a sample with Rigify and I press the button "Generate" get the message:

Fetch rig.
Clear rig animation data.
Duplicate rig: 0.023
Make list of org bones: 0.001
Create root bone: 0.001
Violación de segmento (`core' generado)

And crash blender.

Exact steps for others to reproduce the error

Open a new file.
Active the addon Rigify.
Add a Human (Meta-rig) or other sample (finger, spine, etc.)
Press the button "Generate".
Crash.

**System Information** Ubuntu 14.04 Nvidia 8600gt **Blender Version** Broken: 2.72 3967d1c (compile with scons) **Short description of error** When I add a sample with Rigify and I press the button "Generate" get the message: Fetch rig. Clear rig animation data. Duplicate rig: 0.023 Make list of org bones: 0.001 Create root bone: 0.001 Violación de segmento (`core' generado) And crash blender. **Exact steps for others to reproduce the error** 1. Open a new file. 2. Active the addon Rigify. 3. Add a Human (Meta-rig) or other sample (finger, spine, etc.) 4. Press the button "Generate". 5. Crash.

Jefferson Rausseo commented

2014-11-13 23:01:11 +01:00

Changed status to: 'Open'

Jefferson Rausseo commented

2014-11-13 23:01:11 +01:00

Added subscriber: @jefrau

Bastien Montagne commented

2014-11-14 09:16:12 +01:00

Added subscriber: @mont29

Bastien Montagne commented

2014-11-14 09:16:12 +01:00

Confirmed, will have a look.

Bastien Montagne self-assigned this 2014-11-14 09:16:19 +01:00

Bastien Montagne commented

2014-11-14 15:57:33 +01:00

Dev notes: Gah… already three hours spent on this… Issue is in IDprop. We are facing a corrupted ListBase (two items in list, but listbase->first->next is NULL), which pops out of the blue (meaning, we have hundreds of valid access to that, and suddenly this breaks). So some third party code (i.e. not ListBase one) somehow set that 'next' pointer to NULL, when it should not touch it… :/