59a30d822f
This is an interesting bug since it is likely the cause of many other suspicious python crashes in blender. sys.last_traceback would store references to PyObjects at the point of the crash. it would only free these when sys.last_traceback was set again or on exit. This caused many crashes in the BGE while testing since python would end up freeing invalid game objects - When running scripts with errors, Blender would crash every 2-5 runs - in my test just now it crashed after 4 trys. It could also segfault blender, when (for eg) you run a script that has objects referenced. then load a new file and run another script that raises an error. In this case all the invalid Blender-Object's user counts would be decremented, even though none of the pointers were still valid. |
||
|---|---|---|
| .. | ||
| blender | ||
| creator | ||
| darwin | ||
| gameengine | ||
| icons | ||
| kernel | ||
| CMakeLists.txt | ||
| Makefile | ||
| nan_compile.mk | ||
| nan_definitions.mk | ||
| nan_link.mk | ||
| nan_subdirs.mk | ||
| nan_warn.mk | ||
| SConscript | ||