Motion Trail addon segfaults on debug builds #37767

New Issue

Dalai Felinto · 2013-12-10T14:03:36+01:00

Dalai Felinto commented

2013-12-10 14:03:36 +01:00

System Information
OSX 10.8.5

Blender Version
Broken: my own Debug builds (with Framework Python, or Blender's)
Worked: my own Release builds
Worked: BF official builds (2.69 and builder bot )

Short description of error
I get a segfault while using the Motion Trail addon. System crash log: osx-crash.txt

Exact steps for others to reproduce the error
(you can use this file to skip steps 2 and 3: motiontrail.blend)

you need to install the motion trail addon:
http://developer.blender.org/diffusion/BAC/browse/master/animation_motion_trail.py
(you likely have it already, but in case you don't)

Turn on 'Motion Trail' addon
Select the default Cube
Keyframe location (I), go to frame 250, move cube and re-keyframe location (I)
On the Toolshelf, find 'Motion Trail' panel, select 'Enable Addon'
In Motion Trail panel, increase before/after Frames until you see the motion trail line
Select one of the line dots, move it (G + mouse move).

BOOM, segfaults! System crash log: osx-crash.txt

Error from Python
If I add:

import pdb
pdb.set_trace()

inside view3d_utils.py :: region_2d_to_location_3d, and walk through the steps (pressing n + enter a few times) it crashes right after it calls intersect_line_plane(). It returns the error:

Fatal Python error: deallocating None

Error from C

If I add a breakpoint in M_Geometry_intersect_line_plane and walk through the steps (n + enter a few times) it crashes here:

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0x00000000fb5ce3c7

0x00000001006ef487 in _BaseMathObject_ReadCallback (self=0x100000001) at /Users/dfelinto/blender/git/blender/source/blender/python/mathutils/mathutils.c:361
361 if (LIKELY(cb->get(self, self->cb_subtype) != -1)) {

Notes

It doesn't crash all the times, but when it starts crashing, it takes a lot of restarting, opening different files, ... to get things working again.
I tested it in Linux and Windows and none of them presented problems. It was Release builds though.
It doesn't happen in Release builds (not as easily at least). My building optons: cmake_setup.txt

**System Information** OSX 10.8.5 **Blender Version** Broken: my own Debug builds (with Framework Python, or Blender's) Worked: my own Release builds Worked: BF official builds (2.69 and builder bot ) **Short description of error** I get a segfault while using the Motion Trail addon. System crash log: [osx-crash.txt](https://archive.blender.org/developer/F38210/osx-crash.txt) **Exact steps for others to reproduce the error** (you can use this file to skip steps 2 and 3: [motiontrail.blend](https://archive.blender.org/developer/F38214/motiontrail.blend)) 0. you need to install the motion trail addon: http://developer.blender.org/diffusion/BAC/browse/master/animation_motion_trail.py (you likely have it already, but in case you don't) - Turn on 'Motion Trail' addon - Select the default Cube - Keyframe location (I), go to frame 250, move cube and re-keyframe location (I) - On the Toolshelf, find 'Motion Trail' panel, select 'Enable Addon' - In Motion Trail panel, increase before/after Frames until you see the motion trail line - Select one of the line dots, move it (G + mouse move). BOOM, segfaults! System crash log: [osx-crash.txt](https://archive.blender.org/developer/F38210/osx-crash.txt) **Error from Python** If I add: ``` import pdb pdb.set_trace() ``` inside view3d_utils.py :: region_2d_to_location_3d, and walk through the steps (pressing n + enter a few times) it crashes right after it calls intersect_line_plane(). It returns the error: ``` Fatal Python error: deallocating None ``` **Error from C** If I add a breakpoint in M_Geometry_intersect_line_plane and walk through the steps (n + enter a few times) it crashes here: ``` Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_INVALID_ADDRESS at address: 0x00000000fb5ce3c7 ``` 0x00000001006ef487 in _BaseMathObject_ReadCallback (self=0x100000001) at /Users/dfelinto/blender/git/blender/source/blender/python/mathutils/mathutils.c:361 361 if (LIKELY(cb->get(self, self->cb_subtype) != -1)) { **Notes** * It doesn't crash all the times, but when it starts crashing, it takes a lot of restarting, opening different files, ... to get things working again. * I tested it in Linux and Windows and none of them presented problems. It was Release builds though. * It doesn't happen in Release builds (not as easily at least). My building optons: [cmake_setup.txt](https://archive.blender.org/developer/F38216/cmake_setup.txt)

Dalai Felinto commented

2013-12-10 14:03:36 +01:00

Changed status to: 'Open'