System Information
Archlinux
Blender Version
Broken: 5552e83b53
Worked: 2.78a
Short description of error
numpy arrays make blende crash
Exact steps for others to reproduce the error
execute this 3 lines in the python console of Blender's UI
import numpy a = numpy.array([[3, 2, 0],[3, 1, 0]], dtype=numpy.int32) a[0]
blender crashes.
Crash isn't present on Win7 and MacOS and disappear on Linux if numpy is bumped to 1.12
I can confirm the crash on Ubuntu (see attached system-info.txt and blender.crash.txt)
(this is with the official 2.78b linux download from the site)
@Sergey Sharybin (sergey) so, looks like you’ll have to update your release build environment? ;)
For the records, official numpy version is currently 1.10.1 (afaik, that’s what defined in install_deps.sh anyway).
confirm same issue in 2.78b (numpy 1.10.1 as per latest download from blender site) but not previous versions.
I get same crash executing john peterson sample in python terminal, however if I paste into Text editor it runs ok. However if I alter it to
import numpy a = numpy.array([[3, 2, 0],[3, 1, 0]], dtype=numpy.int32) a[:,0] *= 1
it crashes with the following (don't know if this is relevant or helpful info)
# Blender 2.78 (sub 0), Commit date: 2017-02-08 13:50, Hash 3c043732d3f bpy.context.area.type = 'TEXT_EDITOR' # Property bpy.ops.text.run_script() # Operator # backtrace ./blender(BLI_system_backtrace+0x1d) [0x19aadcd] ./blender() [0x104e3c6] /lib/x86_64-linux-gnu/libc.so.6(+0x354b0) [0x7fa8f984b4b0] /home/patrick/blender/blender-2.78b-linux-glibc219-x86_64/2.78/python/lib/python3.5/site-packages/numpy/core/multiarray.cpython-35m-x86_64-linux-gnu.so(+0x1396d6) [0x7fa8d9f406d6] /home/patrick/blender/blender-2.78b-linux-glibc219-x86_64/2.78/python/lib/python3.5/site-packages/numpy/core/multiarray.cpython-35m-x86_64-linux-gnu.so(+0x13d627) [0x7fa8d9f44627] /home/patrick/blender/blender-2.78b-linux-glibc219-x86_64/2.78/python/lib/python3.5/site-packages/numpy/core/umath.cpython-35m-x86_64-linux-gnu.so(+0x7d7db) [0x7fa8d9ba97db] /home/patrick/blender/blender-2.78b-linux-glibc219-x86_64/2.78/python/lib/python3.5/site-packages/numpy/core/umath.cpython-35m-x86_64-linux-gnu.so(+0x7e708) [0x7fa8d9baa708] ./blender(PyObject_Call+0x3a) [0x290461a] ./blender(PyObject_CallFunctionObjArgs+0x16c) [0x2905a0c] ./blender(PyNumber_InPlaceMultiply+0x34) [0x2901d74] ./blender(PyEval_EvalFrameEx+0xef6) [0x29c8846] ./blender() [0x29d157d] ./blender(PyEval_EvalCode+0x1f) [0x29d167f] ./blender() [0x142d238] ./blender() [0x110d8ee] ./blender() [0x1055b22] ./blender() [0x105604d] ./blender() [0x1222572] ./blender() [0x1232b35] ./blender() [0x1057417] ./blender() [0x1057738] ./blender(wm_event_do_handlers+0x211) [0x1057a81] ./blender(WM_main+0x18) [0x104ef38] ./blender(main+0x3f0) [0xfed710] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7fa8f9836830] ./blender() [0x104b358]
Seems something went wrong with compilation of numpy. Did a fresh git clone of numpy, checked out to v1.10.1 branch (currently official version we bundle) and the issue is now gone.
Oh well, give it a test with latest builds from buildbot and the issue should be gone. Hopefully! :) Let me know.
P.S. Seems managed to address such an annoying issue just before 2.78c. Redoing Linux builds now.