I've gave category: Rendering as I'm not sure where this bug should go. Possibly into OS X specific if it doesn't appear on other platforms.
--- Operating System, Graphics card ---
OS X 10.9; Intel HD5000
--- Blender version with error, and version that worked ---
2.69 - with error; 2.68a - working
--- Short description of error ---
Running Blender render using command line gives a crash (Segmentation fault: 11) when running 2.69. The same command works using 2.68a.
--- Steps for others to reproduce the error (preferably based on attached .blend file) ---
While on Mac OS X:
$ cd dir_with_attached.blend
$ /Applications/Blender/blender.app/Contents/MacOS/blender -b "test.01.blend" -F PNG -x 1 -f 1
Description
Description
Revisions and Commits
Revisions and Commits
Event Timeline
Comment Actions
After more tests I'm pretty sure the problem is with Maya key scheme. When it's turn on and saved to user settings/startup file Blender will crash when starting render from command line.
Comment Actions
I'm able to reproduce it in Linux. Here's the contents of blender.crash.txt
------
# Blender 2.69 (sub 1), Revision: 60966
# backtrace
/usr/lib/blender/blender() [0xbfa72d]
/lib/x86_64-linux-gnu/libc.so.6(+0x364a0) [0x7fb531ba04a0]
/usr/lib/blender/blender(WM_keymap_list_find+0x12) [0xc08a12]
/usr/lib/blender/blender(WM_modalkeymap_add+0x6c) [0xc0934c]
/usr/lib/blender/blender(KeyMaps_new_call+0x21) [0x1802bb1]
/usr/lib/blender/blender(RNA_function_call+0x12) [0x1715372]
/usr/lib/blender/blender() [0xf7cd9e]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyObject_Call+0x7e) [0x7fb5387e207e]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalFrameEx+0x5858) [0x7fb538724a58]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalCodeEx+0x85c) [0x7fb53871ef6c]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalCode+0x3b) [0x7fb53872799b]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(+0x1fd98a) [0x7fb53888598a]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalFrameEx+0x6ef9) [0x7fb5387260f9]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalCodeEx+0x85c) [0x7fb53871ef6c]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalFrameEx+0x767b) [0x7fb53872687b]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalCodeEx+0x85c) [0x7fb53871ef6c]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalFrameEx+0x767b) [0x7fb53872687b]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalFrameEx+0x7796) [0x7fb538726996]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalCodeEx+0x85c) [0x7fb53871ef6c]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalCode+0x3b) [0x7fb53872799b]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(+0x1fd98a) [0x7fb53888598a]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalFrameEx+0x704c) [0x7fb53872624c]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalCodeEx+0x85c) [0x7fb53871ef6c]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalFrameEx+0x767b) [0x7fb53872687b]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalCodeEx+0x85c) [0x7fb53871ef6c]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(+0x971c9) [0x7fb53871f1c9]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyObject_Call+0x7e) [0x7fb5387e207e]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalFrameEx+0x421d) [0x7fb53872341d]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalCodeEx+0x85c) [0x7fb53871ef6c]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalFrameEx+0x767b) [0x7fb53872687b]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalFrameEx+0x7796) [0x7fb538726996]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalCodeEx+0x85c) [0x7fb53871ef6c]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(+0x971c9) [0x7fb53871f1c9]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyObject_Call+0x7e) [0x7fb5387e207e]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalFrameEx+0x421d) [0x7fb53872341d]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalCodeEx+0x85c) [0x7fb53871ef6c]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalFrameEx+0x767b) [0x7fb53872687b]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalFrameEx+0x7796) [0x7fb538726996]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyEval_EvalCodeEx+0x85c) [0x7fb53871ef6c]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(+0x970b6) [0x7fb53871f0b6]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyObject_Call+0x7e) [0x7fb5387e207e]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(_PyObject_CallMethodObjIdArgs+0xcd) [0x7fb538775a8d]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyImport_ImportModuleLevelObject+0x7f4) [0x7fb53875b904]
/usr/lib/x86_64-linux-gnu/libpython3.3m.so.1.0(PyImport_ImportModuleLevel+0x4c) [0x7fb53875be2c]
/usr/lib/blender/blender() [0xf83532]
/usr/lib/blender/blender(BPy_init_modules+0x272) [0xf83802]
/usr/lib/blender/blender(BPY_python_start+0xf8) [0xf743d8]
/usr/lib/blender/blender(WM_init+0xe4) [0xc06f34]
/usr/lib/blender/blender(main+0xc27) [0xbc4947]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed) [0x7fb531b8b76d]
/usr/lib/blender/blender() [0xbf9299]
Comment Actions
Could not reproduce the crash here. Does it happen if you add --factory-startup before -b ?
Comment Actions
As I noted in a comment crash happens when Maya key scheme is selected and saved in preferences.
Crash does not happen after adding --factory-startup.
Comment Actions
Cannot reproduce on OSX 10.9 with Blender 2.69.
/Applications/Blender/blender.app/Contents/MacOS/blender -b "test.01.blend" -F PNG -x 1 -f 1
just renders me the cube with transparent background, saves it as .png and exits without error.
Jens
Comment Actions
For me 2.69 on OS X Mavericks does not segfault with or without "Maya key scheme is selected and saved in preferences"
same command as Jens same result.