blender/blender
blender/blender
192
601
Fork 939
Code Issues 6.3k Pull Requests 1.1k Projects 22 Wiki Activity

Crash during autocompletion in PyConsole (Linux Library Compatibility) #43491

New Issue
Closed
opened 2015-01-30 23:23:36 +01:00 by 3dvits@gmail.com · 63 comments
3dvits@gmail.com commented 2015-01-30 23:23:36 +01:00
Copy Link

System Information
Ubuntu 14.04 x86 with Linux kernel 3.11.0-17

Blender Version
Broken: starting with Blender 2.71
Bug not reproduced on Blender older than 2.70 and on x86_64 Linux system

Short description of error
After pressing Autocompletion button or "Ctrl+Space" shortcut in blender Python Console, Blender immediately crashed

Exact steps for others to reproduce the error

  1. Open blender
  2. Switch to Python Console window
  3. Write "bpy." and press "Autocompletion" button or "Ctrl+Space" shortcut and Blender immediately crashed.
    blender.crash.txt
**System Information** Ubuntu 14.04 x86 with Linux kernel 3.11.0-17 **Blender Version** Broken: starting with Blender 2.71 Bug not reproduced on Blender older than 2.70 and on x86_64 Linux system **Short description of error** After pressing Autocompletion button or "Ctrl+Space" shortcut in blender Python Console, Blender immediately crashed **Exact steps for others to reproduce the error** 1) Open blender 2) Switch to Python Console window 3) Write "bpy." and press "Autocompletion" button or "Ctrl+Space" shortcut and Blender immediately crashed. [blender.crash.txt](https://archive.blender.org/developer/F140029/blender.crash.txt)
3dvits@gmail.com commented 2015-01-30 23:23:36 +01:00
Author
Copy Link

Changed status to: 'Open'

Changed status to: 'Open'
3dvits@gmail.com commented 2015-01-30 23:23:36 +01:00
Author
Copy Link

Added subscriber: @VitaliiShmorgun

Added subscriber: @VitaliiShmorgun
Aaron Carlisle commented 2015-01-31 19:06:36 +01:00
Member
Copy Link

Added subscriber: @Blendify

Added subscriber: @Blendify
Kévin Dietrich commented 2015-01-31 23:44:59 +01:00
Member
Copy Link

Added subscriber: @kevindietrich

Added subscriber: @kevindietrich
Kévin Dietrich commented 2015-01-31 23:44:59 +01:00
Member
Copy Link

I cannot reproduce this here (Mint 17 64 bits, latest head) with either a debug or release build.

I cannot reproduce this here (Mint 17 64 bits, latest head) with either a debug or release build.
3dvits@gmail.com commented 2015-01-31 23:57:36 +01:00
Author
Copy Link

I have written: "Bug not reproduced on Blender older than 2.70 and on x86_64 Linux system"
It means, bug not reproduced on 64 bit system

I have written: "Bug not reproduced on Blender older than 2.70 and on x86_64 Linux system" It means, bug not reproduced on 64 bit system
Kévin Dietrich commented 2015-02-01 04:32:37 +01:00
Member
Copy Link

Oops, I misread the report :), I'll try and check on my 32-bit laptop.

Oops, I misread the report :), I'll try and check on my 32-bit laptop.
Campbell Barton commented 2015-02-01 12:00:22 +01:00
Owner
Copy Link

Added subscriber: @ideasman42

Added subscriber: @ideasman42
Campbell Barton commented 2015-02-01 12:00:22 +01:00
Owner
Copy Link

Could you test with 2.73a?

Could you test with 2.73a?
3dvits@gmail.com commented 2015-02-01 15:51:52 +01:00
Author
Copy Link

Could you test with 2.73a?

Already tested. Bug reproduced in blender in versions from 2.71 to 2.73a on 32 bit Ubuntu 14.04

> Could you test with 2.73a? Already tested. Bug reproduced in blender in versions from 2.71 to 2.73a on 32 bit Ubuntu 14.04
Giuseppe De Marco commented 2015-02-02 11:23:45 +01:00
Copy Link

Added subscriber: @demarcog83

Added subscriber: @demarcog83
Giuseppe De Marco commented 2015-02-02 11:23:45 +01:00
Copy Link

System:
Description: Debian GNU/Linux 8.0 (jessie)
Release: 8.0

Linux flybook 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt2-1 (2014-12-08) x86_64 GNU/Linux

Autocomplete crashes with 2.72 and 2.73a, all binaries from official repo.
It also crashed with 2 feb 2015 dailybuild named blender-2.73-0305b20-linux-glibc211-x86_64.

Only Blender 2.70 works with autocomplete feature.

Is there any compilation workaround for 2.72 / 2.73 ?

In stdout I can read "Segmentation error".

Here is the crash log:

# Blender 2.72 (sub 0), Commit date: 1970-01-01 00:00, Hash unknown

# backtrace
blender() [0x901818]
/lib/x86_64-linux-gnu/libc.so.6(+0x35180) [0x7f997f73c180]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyModule_GetState+0xb) [0x7f9985fda4eb]
/usr/lib/python3.4/lib-dynload/readline.cpython-34m-x86_64-linux-gnu.so(+0x3984) [0x7f9960174984]
/usr/lib/x86_64-linux-gnu/libedit.so.2(rl_initialize+0x2d1) [0x7f9961912d51]
/usr/lib/python3.4/lib-dynload/readline.cpython-34m-x86_64-linux-gnu.so(+0x2b9d) [0x7f9960173b9d]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(_PyImport_LoadDynamicModule+0x113) [0x7f99860cbcd3]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(+0x199f35) [0x7f99860cbf35]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x58d5) [0x7f998611bc85]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalCodeEx+0x883) [0x7f998611eaa3]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x6071) [0x7f998611c421]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalCodeEx+0x883) [0x7f998611eaa3]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(+0xd90e6) [0x7f998600b0e6]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyObject_Call+0x68) [0x7f9986041cd8]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0xfa3) [0x7f9986117353]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalCodeEx+0x883) [0x7f998611eaa3]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x6071) [0x7f998611c421]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x685c) [0x7f998611cc0c]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x685c) [0x7f998611cc0c]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x685c) [0x7f998611cc0c]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalCodeEx+0x883) [0x7f998611eaa3]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(+0xd8ff9) [0x7f998600aff9]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyObject_Call+0x68) [0x7f9986041cd8]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(_PyObject_CallMethodIdObjArgs+0x15f) [0x7f99860bd34f]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyImport_ImportModuleLevelObject+0x7f4) [0x7f99860cb474]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyImport_ImportModuleLevel+0x39) [0x7f99860cb859]
blender() [0xcfae72]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyObject_Call+0x68) [0x7f9986041cd8]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_CallObjectWithKeywords+0x47) [0x7f9986115787]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x279f) [0x7f9986118b4f]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalCodeEx+0x883) [0x7f998611eaa3]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalCode+0x1b) [0x7f998611eb4b]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(+0x229cd5) [0x7f998615bcd5]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x58d5) [0x7f998611bc85]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalCodeEx+0x883) [0x7f998611eaa3]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x6071) [0x7f998611c421]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x685c) [0x7f998611cc0c]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x685c) [0x7f998611cc0c]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x685c) [0x7f998611cc0c]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x685c) [0x7f998611cc0c]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalCodeEx+0x883) [0x7f998611eaa3]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(+0xd8ff9) [0x7f998600aff9]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyObject_Call+0x68) [0x7f9986041cd8]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(_PyObject_CallMethodIdObjArgs+0x15f) [0x7f99860bd34f]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyImport_ImportModuleLevelObject+0x7f4) [0x7f99860cb474]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyImport_ImportModuleLevel+0x39) [0x7f99860cb859]
blender() [0xcfae72]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyObject_Call+0x68) [0x7f9986041cd8]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_CallObjectWithKeywords+0x47) [0x7f9986115787]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x279f) [0x7f9986118b4f]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalCodeEx+0x883) [0x7f998611eaa3]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalCode+0x1b) [0x7f998611eb4b]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(+0x229cd5) [0x7f998615bcd5]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x58d5) [0x7f998611bc85]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalCodeEx+0x883) [0x7f998611eaa3]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x6071) [0x7f998611c421]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x685c) [0x7f998611cc0c]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x685c) [0x7f998611cc0c]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x685c) [0x7f998611cc0c]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x685c) [0x7f998611cc0c]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalCodeEx+0x883) [0x7f998611eaa3]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(+0xd8ff9) [0x7f998600aff9]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyObject_Call+0x68) [0x7f9986041cd8]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(_PyObject_CallMethodIdObjArgs+0x15f) [0x7f99860bd34f]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyImport_ImportModuleLevelObject+0x7f4) [0x7f99860cb474]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyImport_ImportModuleLevel+0x39) [0x7f99860cb859]
blender() [0xcfae72]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x58d5) [0x7f998611bc85]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalCodeEx+0x883) [0x7f998611eaa3]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x6071) [0x7f998611c421]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalCodeEx+0x883) [0x7f998611eaa3]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(+0xd8ff9) [0x7f998600aff9]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyObject_Call+0x68) [0x7f9986041cd8]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(_PyObject_CallMethodIdObjArgs+0x15f) [0x7f99860bd34f]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyImport_ImportModuleLevelObject+0x6ad) [0x7f99860cb32d]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyImport_ImportModuleLevel+0x39) [0x7f99860cb859]
blender() [0xcfae72]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyObject_Call+0x68) [0x7f9986041cd8]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_CallObjectWithKeywords+0x47) [0x7f9986115787]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x279f) [0x7f9986118b4f]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x685c) [0x7f998611cc0c]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalCodeEx+0x883) [0x7f998611eaa3]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x6071) [0x7f998611c421]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x685c) [0x7f998611cc0c]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalCodeEx+0x883) [0x7f998611eaa3]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(+0xd8ff9) [0x7f998600aff9]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyObject_Call+0x68) [0x7f9986041cd8]
blender() [0xcda37e]
blender() [0x11867d6]
blender() [0x909f62]
blender() [0x90b2ea]
blender() [0x90b711]
blender() [0x90bc58]
blender(wm_event_do_handlers+0x3e4) [0x90c184]
blender(WM_main+0x18) [0x903c18]
blender(main+0xd93) [0x8ea983]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f997f728b45]
blender() [0x9012c4]
}
System: Description: Debian GNU/Linux 8.0 (jessie) Release: 8.0 Linux flybook 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt2-1 (2014-12-08) x86_64 GNU/Linux Autocomplete crashes with 2.72 and 2.73a, all binaries from official repo. It also crashed with 2 feb 2015 dailybuild named blender-2.73-0305b20-linux-glibc211-x86_64. Only Blender 2.70 works with autocomplete feature. Is there any compilation workaround for 2.72 / 2.73 ? In stdout I can read "Segmentation error". Here is the crash log: ``` # Blender 2.72 (sub 0), Commit date: 1970-01-01 00:00, Hash unknown # backtrace blender() [0x901818] /lib/x86_64-linux-gnu/libc.so.6(+0x35180) [0x7f997f73c180] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyModule_GetState+0xb) [0x7f9985fda4eb] /usr/lib/python3.4/lib-dynload/readline.cpython-34m-x86_64-linux-gnu.so(+0x3984) [0x7f9960174984] /usr/lib/x86_64-linux-gnu/libedit.so.2(rl_initialize+0x2d1) [0x7f9961912d51] /usr/lib/python3.4/lib-dynload/readline.cpython-34m-x86_64-linux-gnu.so(+0x2b9d) [0x7f9960173b9d] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(_PyImport_LoadDynamicModule+0x113) [0x7f99860cbcd3] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(+0x199f35) [0x7f99860cbf35] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x58d5) [0x7f998611bc85] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalCodeEx+0x883) [0x7f998611eaa3] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x6071) [0x7f998611c421] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalCodeEx+0x883) [0x7f998611eaa3] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(+0xd90e6) [0x7f998600b0e6] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyObject_Call+0x68) [0x7f9986041cd8] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0xfa3) [0x7f9986117353] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalCodeEx+0x883) [0x7f998611eaa3] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x6071) [0x7f998611c421] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x685c) [0x7f998611cc0c] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x685c) [0x7f998611cc0c] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x685c) [0x7f998611cc0c] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalCodeEx+0x883) [0x7f998611eaa3] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(+0xd8ff9) [0x7f998600aff9] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyObject_Call+0x68) [0x7f9986041cd8] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(_PyObject_CallMethodIdObjArgs+0x15f) [0x7f99860bd34f] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyImport_ImportModuleLevelObject+0x7f4) [0x7f99860cb474] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyImport_ImportModuleLevel+0x39) [0x7f99860cb859] blender() [0xcfae72] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyObject_Call+0x68) [0x7f9986041cd8] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_CallObjectWithKeywords+0x47) [0x7f9986115787] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x279f) [0x7f9986118b4f] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalCodeEx+0x883) [0x7f998611eaa3] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalCode+0x1b) [0x7f998611eb4b] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(+0x229cd5) [0x7f998615bcd5] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x58d5) [0x7f998611bc85] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalCodeEx+0x883) [0x7f998611eaa3] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x6071) [0x7f998611c421] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x685c) [0x7f998611cc0c] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x685c) [0x7f998611cc0c] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x685c) [0x7f998611cc0c] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x685c) [0x7f998611cc0c] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalCodeEx+0x883) [0x7f998611eaa3] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(+0xd8ff9) [0x7f998600aff9] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyObject_Call+0x68) [0x7f9986041cd8] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(_PyObject_CallMethodIdObjArgs+0x15f) [0x7f99860bd34f] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyImport_ImportModuleLevelObject+0x7f4) [0x7f99860cb474] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyImport_ImportModuleLevel+0x39) [0x7f99860cb859] blender() [0xcfae72] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyObject_Call+0x68) [0x7f9986041cd8] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_CallObjectWithKeywords+0x47) [0x7f9986115787] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x279f) [0x7f9986118b4f] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalCodeEx+0x883) [0x7f998611eaa3] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalCode+0x1b) [0x7f998611eb4b] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(+0x229cd5) [0x7f998615bcd5] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x58d5) [0x7f998611bc85] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalCodeEx+0x883) [0x7f998611eaa3] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x6071) [0x7f998611c421] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x685c) [0x7f998611cc0c] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x685c) [0x7f998611cc0c] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x685c) [0x7f998611cc0c] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x685c) [0x7f998611cc0c] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalCodeEx+0x883) [0x7f998611eaa3] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(+0xd8ff9) [0x7f998600aff9] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyObject_Call+0x68) [0x7f9986041cd8] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(_PyObject_CallMethodIdObjArgs+0x15f) [0x7f99860bd34f] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyImport_ImportModuleLevelObject+0x7f4) [0x7f99860cb474] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyImport_ImportModuleLevel+0x39) [0x7f99860cb859] blender() [0xcfae72] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x58d5) [0x7f998611bc85] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalCodeEx+0x883) [0x7f998611eaa3] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x6071) [0x7f998611c421] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalCodeEx+0x883) [0x7f998611eaa3] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(+0xd8ff9) [0x7f998600aff9] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyObject_Call+0x68) [0x7f9986041cd8] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(_PyObject_CallMethodIdObjArgs+0x15f) [0x7f99860bd34f] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyImport_ImportModuleLevelObject+0x6ad) [0x7f99860cb32d] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyImport_ImportModuleLevel+0x39) [0x7f99860cb859] blender() [0xcfae72] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyObject_Call+0x68) [0x7f9986041cd8] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_CallObjectWithKeywords+0x47) [0x7f9986115787] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x279f) [0x7f9986118b4f] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x685c) [0x7f998611cc0c] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalCodeEx+0x883) [0x7f998611eaa3] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x6071) [0x7f998611c421] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x685c) [0x7f998611cc0c] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalCodeEx+0x883) [0x7f998611eaa3] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(+0xd8ff9) [0x7f998600aff9] /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyObject_Call+0x68) [0x7f9986041cd8] blender() [0xcda37e] blender() [0x11867d6] blender() [0x909f62] blender() [0x90b2ea] blender() [0x90b711] blender() [0x90bc58] blender(wm_event_do_handlers+0x3e4) [0x90c184] blender(WM_main+0x18) [0x903c18] blender(main+0xd93) [0x8ea983] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f997f728b45] blender() [0x9012c4] } ```
Campbell Barton commented 2015-02-02 14:44:56 +01:00
Owner
Copy Link

Tested with 2.73 release and 5030daf2a8 - both work fine here. Valgrind also doesn't report any errors.

Tested with 2.73 release and 5030daf2a8 - both work fine here. Valgrind also doesn't report any errors.
Clouclou commented 2015-02-02 16:35:18 +01:00
Copy Link

Added subscriber: @clouclou-2

Added subscriber: @clouclou-2
Clouclou commented 2015-02-02 16:35:18 +01:00
Copy Link

On a Debian Jessis 32bits i also have the crash.

I have the crash with 2.72b (system blender) and with the builder version (2.73-64124ba)

Launched with valgrind i have this log:


==2948== Invalid read of size 4
==2948==    at 0xAD73F38: PyModule_GetState (in /tmp/bf/blender-2.73-64124ba-linux-glibc211-i686/blender)
==2948==    by 0x5BD7716: ??? (in /tmp/bf/blender-2.73-64124ba-linux-glibc211-i686/2.73/python/lib/python3.4/lib-dynload/readline.cpython-34m.so)
==2948==    by 0x7BF73C1: rl_initialize (in /usr/lib/i386-linux-gnu/libedit.so.2.0.51)
==2948==    by 0x5BD86E8: PyInit_readline (in /tmp/bf/blender-2.73-64124ba-linux-glibc211-i686/2.73/python/lib/python3.4/lib-dynload/readline.cpython-34m.so)
==2948==    by 0xADF51A4: _PyImport_LoadDynamicModule (in /tmp/bf/blender-2.73-64124ba-linux-glibc211-i686/blender)
==2948==    by 0xADF1CD6: ??? (in /tmp/bf/blender-2.73-64124ba-linux-glibc211-i686/blender)
==2948==    by 0xADDB0A6: PyEval_EvalFrameEx (in /tmp/bf/blender-2.73-64124ba-linux-glibc211-i686/blender)
==2948==    by 0xADD50B4: PyEval_EvalCodeEx (in /tmp/bf/blender-2.73-64124ba-linux-glibc211-i686/blender)
==2948==    by 0xADDAE93: PyEval_EvalFrameEx (in /tmp/bf/blender-2.73-64124ba-linux-glibc211-i686/blender)
==2948==    by 0xADD50B4: PyEval_EvalCodeEx (in /tmp/bf/blender-2.73-64124ba-linux-glibc211-i686/blender)
==2948==    by 0xAD575DF: ??? (in /tmp/bf/blender-2.73-64124ba-linux-glibc211-i686/blender)
==2948==    by 0xAD31CF6: PyObject_Call (in /tmp/bf/blender-2.73-64124ba-linux-glibc211-i686/blender)
==2948==  Address 0x4 is not stack'd, malloc'd or (recently) free'd

(Full log http://www.pasteall.org/56439 )

On a Debian Jessis 32bits i also have the crash. I have the crash with 2.72b (system blender) and with the builder version (2.73-64124ba) Launched with valgrind i have this log: ``` ==2948== Invalid read of size 4 ==2948== at 0xAD73F38: PyModule_GetState (in /tmp/bf/blender-2.73-64124ba-linux-glibc211-i686/blender) ==2948== by 0x5BD7716: ??? (in /tmp/bf/blender-2.73-64124ba-linux-glibc211-i686/2.73/python/lib/python3.4/lib-dynload/readline.cpython-34m.so) ==2948== by 0x7BF73C1: rl_initialize (in /usr/lib/i386-linux-gnu/libedit.so.2.0.51) ==2948== by 0x5BD86E8: PyInit_readline (in /tmp/bf/blender-2.73-64124ba-linux-glibc211-i686/2.73/python/lib/python3.4/lib-dynload/readline.cpython-34m.so) ==2948== by 0xADF51A4: _PyImport_LoadDynamicModule (in /tmp/bf/blender-2.73-64124ba-linux-glibc211-i686/blender) ==2948== by 0xADF1CD6: ??? (in /tmp/bf/blender-2.73-64124ba-linux-glibc211-i686/blender) ==2948== by 0xADDB0A6: PyEval_EvalFrameEx (in /tmp/bf/blender-2.73-64124ba-linux-glibc211-i686/blender) ==2948== by 0xADD50B4: PyEval_EvalCodeEx (in /tmp/bf/blender-2.73-64124ba-linux-glibc211-i686/blender) ==2948== by 0xADDAE93: PyEval_EvalFrameEx (in /tmp/bf/blender-2.73-64124ba-linux-glibc211-i686/blender) ==2948== by 0xADD50B4: PyEval_EvalCodeEx (in /tmp/bf/blender-2.73-64124ba-linux-glibc211-i686/blender) ==2948== by 0xAD575DF: ??? (in /tmp/bf/blender-2.73-64124ba-linux-glibc211-i686/blender) ==2948== by 0xAD31CF6: PyObject_Call (in /tmp/bf/blender-2.73-64124ba-linux-glibc211-i686/blender) ==2948== Address 0x4 is not stack'd, malloc'd or (recently) free'd ``` (Full log http://www.pasteall.org/56439 )
Julian Eisel commented 2015-02-03 14:47:03 +01:00
Member
Copy Link

Added subscriber: @JulianEisel

Added subscriber: @JulianEisel
Julian Eisel commented 2015-02-03 14:47:03 +01:00
Member
Copy Link

Also can't reproduce this here. Maybe you guys should try using factory settings? Doesn't really look like this from the error log, but chances are this is caused by an addon (although I have no idea how an error log from an addon crash would look like).

Also can't reproduce this here. Maybe you guys should try using factory settings? Doesn't really look like this from the error log, but chances are this is caused by an addon (although I have no idea how an error log from an addon crash would look like).
Clouclou commented 2015-02-03 14:51:32 +01:00
Copy Link

When i reproduced it, i used a fresh install (it was a virtual machine) where i never launch Blender on it. So it mean i have a the factory settings and i don't have any extra addon.

When i reproduced it, i used a fresh install (it was a virtual machine) where i never launch Blender on it. So it mean i have a the factory settings and i don't have any extra addon.
Giuseppe De Marco commented 2015-02-04 17:40:32 +01:00
Copy Link

It crashes also with a factory default startup file, with no additional addons.
Only 2.70 version doesn't crash, now I'm coding on this.

This debian jessie uses:

libc6:amd64 2.19-13
python3 3.4.2-2
readline-common 6.3-8

Is there any critical information I can give you that could help us to analyze this issue ?

It crashes also with a factory default startup file, with no additional addons. Only 2.70 version doesn't crash, now I'm coding on this. This debian jessie uses: libc6:amd64 2.19-13 python3 3.4.2-2 readline-common 6.3-8 Is there any critical information I can give you that could help us to analyze this issue ?
Thomas commented 2015-02-08 20:12:10 +01:00
Copy Link

Added subscriber: @zoschfrosch

Added subscriber: @zoschfrosch
Thomas commented 2015-02-08 20:12:10 +01:00
Copy Link

On Ubuntu 14.10 64 bit, I also have the crash. The installed blender version is 2.70a. With 2.73a, it crashes too. With an older version (2.63a), autocompletion works fine.

On Ubuntu 14.10 64 bit, I also have the crash. The installed blender version is 2.70a. With 2.73a, it crashes too. With an older version (2.63a), autocompletion works fine.
Giuseppe De Marco commented 2015-02-09 18:32:18 +01:00
Copy Link

Now autocomplete in python console in blender 2.73a on my debian jessie amd64 works but I compiled blender from scratch.
The problem, probably, is an incompatibility between a library updates and the linked static of the official version of blender, downloaded from web.

Maybe the official solution to solve this problem is to download blender sources from the web and, in its decompressed directory, start:

./build_files/build_environment/install_deps.sh

I've noticed this because after this compilation the other blender versions, that were downloaded as compiled static from the web, now works with autocomplete,

good news

Now autocomplete in python console in blender 2.73a on my debian jessie amd64 works but I compiled blender from scratch. The problem, probably, is an incompatibility between a library updates and the linked static of the official version of blender, downloaded from web. Maybe the official solution to solve this problem is to download blender sources from the web and, in its decompressed directory, start: ./build_files/build_environment/install_deps.sh I've noticed this because after this compilation the other blender versions, that were downloaded as compiled static from the web, now works with autocomplete, good news
Giuseppe De Marco commented 2015-02-09 18:48:32 +01:00
Copy Link

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Giuseppe De Marco self-assigned this 2015-02-09 18:48:32 +01:00
Giuseppe De Marco commented 2015-02-09 18:48:32 +01:00
Copy Link

Yes, if someone could test as I made we could think of it as completely solved

Yes, if someone could test as I made we could think of it as completely solved
Thomas commented 2015-02-09 20:19:40 +01:00
Copy Link

I compiled blender 2.73a from scratch on my Ubuntu 14.10 64 bit. I started the install_deps.sh script, but I still had to install a lot of dev libraries because I got file not found errors for some .h files. Finally, I succeeded compiling, but the autocompletion crash is still there.
What can I try next? Compiling with debug information and try to find the segmentation fault in a debugger? Or are there command line options for logging?

I compiled blender 2.73a from scratch on my Ubuntu 14.10 64 bit. I started the install_deps.sh script, but I still had to install a lot of dev libraries because I got file not found errors for some .h files. Finally, I succeeded compiling, but the autocompletion crash is still there. What can I try next? Compiling with debug information and try to find the segmentation fault in a debugger? Or are there command line options for logging?
Julian Eisel commented 2015-02-09 20:28:02 +01:00
Member
Copy Link

Changed status from 'Resolved' to: 'Archived'

Changed status from 'Resolved' to: 'Archived'
Julian Eisel commented 2015-02-09 20:28:02 +01:00
Member
Copy Link

Something to note here: It wasn't clear to me that you are using own builds, for which reports in our tracker are not allowed. So even if the crashes still occur, we won't reopen until it's proven they also occur on "official" builds. That doesn't mean it's not allowed for you to go on discussing this though (as long as it doesn't get too much), we just won't reopen.

Something to note here: It wasn't clear to me that you are using own builds, for which reports in our tracker are not allowed. So even if the crashes still occur, we won't reopen until it's proven they also occur on "official" builds. That doesn't mean it's not allowed for you to go on discussing this though (as long as it doesn't get too much), we just won't reopen.
Thomas commented 2015-02-09 23:04:59 +01:00
Copy Link

Maybe this is a misunderstanding. I wanted to begin programming blender python and used the official version 2.70a which is installed with Ubuntu 14.10. Because it crashed on code completion, I tried the official binary 2.73a, it also crashes on my Ubuntu. Then I googled and found this bug report - only compiled from source to test if there's a library problem. With the older official version 2.63a, code completion works as designed.

Maybe this is a misunderstanding. I wanted to begin programming blender python and used the official version 2.70a which is installed with Ubuntu 14.10. Because it crashed on code completion, I tried the official binary 2.73a, it also crashes on my Ubuntu. Then I googled and found this bug report - only compiled from source to test if there's a library problem. With the older official version 2.63a, code completion works as designed.
Campbell Barton commented 2015-02-10 06:22:15 +01:00
Owner
Copy Link

@JulianEisel, re: we won't reopen until it's proven they also occur on "official" builds

I don't completely agree, if users apply patches or use unsupported library versions - then we can't support.
But if they use an un-modified codebase on a recent OS and Blender is crashing, then it may well be a bug, so we should try to fix still. (eg #39245)

In this case the crash is outside of Blender so it could be some library conflict - in this case, but we should still try to resolve somehow.

@zoschfrosch

Some things you could try:

  • remove /home/vit/prog/blender-2.73a-linux-glibc211-i686/2.73/python
  • Do a lite build make lite if this works, then it may be some library conflict.

Since the official download from Blender.org works (other Linux distros work too) and Ubuntu's package crashes, you should raise this issue with Debian/Ubuntu maintainers.

Please post a link to the Debian/Ubuntu bug report here.

@JulianEisel, re: `we won't reopen until it's proven they also occur on "official" builds` I don't completely agree, if users apply patches or use unsupported library versions - then we can't support. But if they use an un-modified codebase on a recent OS and Blender is crashing, then it may well be a bug, so we should try to fix still. (eg #39245) In this case the crash is outside of Blender so it could be some library conflict - in this case, but we should still try to resolve somehow. @zoschfrosch Some things you could try: - remove /home/vit/prog/blender-2.73a-linux-glibc211-i686/2.73/python - Do a lite build `make lite` if this works, then it may be some library conflict. Since the official download from Blender.org works (other Linux distros work too) and Ubuntu's package crashes, you should raise this issue with Debian/Ubuntu maintainers. Please post a link to the Debian/Ubuntu bug report here.
Campbell Barton commented 2015-02-10 06:22:55 +01:00
Owner
Copy Link

Changed status from 'Archived' to: 'Open'

Changed status from 'Archived' to: 'Open'
Campbell Barton commented 2015-02-10 09:02:36 +01:00
Owner
Copy Link

Tried building today's master - 6971bd9a4f on Ubuntu14.04 (server edition).
and couldn't redo the crash.

Tried building today's master - 6971bd9a4f on Ubuntu14.04 (server edition). and couldn't redo the crash.
3dvits@gmail.com commented 2015-02-10 09:39:07 +01:00
Author
Copy Link

Since the official download from Blender.org works (other Linux distros work too) and Ubuntu's package crashes, you should raise this issue with Debian/Ubuntu maintainers.

In Ubuntu 14.04 repositories Blender version 2.63. As far as I can see, this bug not reproduced in this version of blender. That is why maintainers of Ubuntu can not help us.
The problem once again occurs in versions from blender.org 2.71 - 2.73a

> Since the official download from Blender.org works (other Linux distros work too) and Ubuntu's package crashes, you should raise this issue with Debian/Ubuntu maintainers. In Ubuntu 14.04 repositories Blender version 2.63. As far as I can see, this bug not reproduced in this version of blender. That is why maintainers of Ubuntu can not help us. The problem once again occurs in versions from blender.org 2.71 - 2.73a
Giuseppe De Marco commented 2015-02-10 09:53:08 +01:00
Copy Link

In #43491#287756, @zoschfrosch wrote:
I compiled blender 2.73a from scratch on my Ubuntu 14.10 64 bit. I started the install_deps.sh script, but I still had to install a lot of dev libraries because I got file not found errors for some .h files. Finally, I succeeded compiling, but the autocompletion crash is still there.
What can I try next? Compiling with debug information and try to find the segmentation fault in a debugger? Or are there command line options for logging?

Try to clean all and rebuild, if you compile your own and this still crashes isn't it a library versioning/bug problem ?
And, the important question is, after this, when you've compiled your own, the static official blender does still crash ?

> In #43491#287756, @zoschfrosch wrote: > I compiled blender 2.73a from scratch on my Ubuntu 14.10 64 bit. I started the install_deps.sh script, but I still had to install a lot of dev libraries because I got file not found errors for some .h files. Finally, I succeeded compiling, but the autocompletion crash is still there. > What can I try next? Compiling with debug information and try to find the segmentation fault in a debugger? Or are there command line options for logging? Try to clean all and rebuild, if you compile your own and this still crashes isn't it a library versioning/bug problem ? And, the important question is, after this, when you've compiled your own, the static official blender does still crash ?
Campbell Barton commented 2015-02-10 12:09:10 +01:00
Owner
Copy Link

Note, that I didn't use install_deps.sh - Instread I installed deps from ubuntu, see: http://wiki.blender.org/index.php/Dev:Doc/Building_Blender/Linux/Ubuntu/CMake#Manual_dependencies_installation

Though this doesn't include OpenImageIO, so I had to disable Cycles.

Note, that I didn't use `install_deps.sh` - Instread I installed deps from ubuntu, see: http://wiki.blender.org/index.php/Dev:Doc/Building_Blender/Linux/Ubuntu/CMake#Manual_dependencies_installation Though this doesn't include OpenImageIO, so I had to disable Cycles.
Giuseppe De Marco commented 2015-02-10 12:14:03 +01:00
Copy Link

In #43491#287894, @ideasman42 wrote:
Note, that I didn't use install_deps.sh - Instread I installed deps from ubuntu, see: http://wiki.blender.org/index.php/Dev:Doc/Building_Blender/Linux/Ubuntu/CMake#Manual_dependencies_installation

Though this doesn't include OpenImageIO, so I had to disable Cycles.

Please try
install_deps.sh

> In #43491#287894, @ideasman42 wrote: > Note, that I didn't use `install_deps.sh` - Instread I installed deps from ubuntu, see: http://wiki.blender.org/index.php/Dev:Doc/Building_Blender/Linux/Ubuntu/CMake#Manual_dependencies_installation > > Though this doesn't include OpenImageIO, so I had to disable Cycles. Please try install_deps.sh
Thomas commented 2015-02-10 21:51:17 +01:00
Copy Link

Tried out a lot of things, with the following results:
UbuntuStudio 14.10:
The blender 2.70a from the ubuntu repositories crashes
The static official blender 2.73a crashes
A clean build from sources 2.73a crashes
An older blender 2.63a which I have on another partition (it came with ubuntustudio 13.04) works with ubuntu 14.10
Then I compiled the 2.73a as debug, ran it with gdb, and produced a stack trace after the crash:

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff759a4eb in PyModule_GetState () from /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0
(gdb) bt
- 0  0x00007ffff759a4eb in PyModule_GetState () from /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0
- 1  0x00007fffca435984 in ?? () from /home/thomas/install/linux/2.73/python/lib/python3.4/lib-dynload/readline.cpython-34m-x86_64-linux-gnu.so
#2  0x00007fffd48aa365 in rl_initialize () from /usr/lib/x86_64-linux-gnu/libedit.so.2
...

Next try was to run the official blender 2.73a build with ubuntustudio 13.04: No crash!
I guess there's a problem with the python3.4 shared library and ubuntu 14.10, because on ubuntu 13.04 there is no python 3.4 so.
Then I tried ldd with the different blender version. Only the self compiled versions need the python 3.4 shared library.

Last thing I tried was renaming the ubuntu python shared libraries and starting the official blender 2.73a. It crashed again. But what python library does it use?

Any ideas or hints?

Tried out a lot of things, with the following results: UbuntuStudio 14.10: The blender 2.70a from the ubuntu repositories crashes The static official blender 2.73a crashes A clean build from sources 2.73a crashes An older blender 2.63a which I have on another partition (it came with ubuntustudio 13.04) works with ubuntu 14.10 Then I compiled the 2.73a as debug, ran it with gdb, and produced a stack trace after the crash: ``` Program received signal SIGSEGV, Segmentation fault. 0x00007ffff759a4eb in PyModule_GetState () from /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0 (gdb) bt - 0 0x00007ffff759a4eb in PyModule_GetState () from /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0 - 1 0x00007fffca435984 in ?? () from /home/thomas/install/linux/2.73/python/lib/python3.4/lib-dynload/readline.cpython-34m-x86_64-linux-gnu.so #2 0x00007fffd48aa365 in rl_initialize () from /usr/lib/x86_64-linux-gnu/libedit.so.2 ... ``` Next try was to run the official blender 2.73a build with ubuntustudio 13.04: No crash! I guess there's a problem with the python3.4 shared library and ubuntu 14.10, because on ubuntu 13.04 there is no python 3.4 so. Then I tried ldd with the different blender version. Only the self compiled versions need the python 3.4 shared library. Last thing I tried was renaming the ubuntu python shared libraries and starting the official blender 2.73a. It crashed again. But what python library does it use? Any ideas or hints?
Aaron Carlisle commented 2015-02-11 00:01:31 +01:00
Member
Copy Link

Removed subscriber: @Blendify

Removed subscriber: @Blendify
Giuseppe De Marco commented 2015-02-11 09:31:22 +01:00
Copy Link

Probably takes a library from the system and this cause segmentation fault.

Try to run it with fake env variables, ex

LD_LIBRARY_PATH=/all/but/usr/lib: ./blender

This prevent the use of system libs.
Sorry if I ask you again, have you used install_deps.sh script for update and install requirements ?

Probably takes a library from the system and this cause segmentation fault. Try to run it with fake env variables, ex LD_LIBRARY_PATH=/all/but/usr/lib: ./blender This prevent the use of system libs. Sorry if I ask you again, have you used install_deps.sh script for update and install requirements ?
Thomas commented 2015-02-11 19:22:08 +01:00
Copy Link

Faking the library path, it crashes again. And yes, I have used install_deps.sh.

Faking the library path, it crashes again. And yes, I have used install_deps.sh.
Campbell Barton commented 2015-02-12 11:37:32 +01:00
Owner
Copy Link

Tested using install_deps.sh and can't redo the crash there either. (Ubuntu 14.04, 32bit)

Tested using `install_deps.sh` and can't redo the crash there either. (Ubuntu 14.04, 32bit)
Clouclou commented 2015-02-12 11:38:15 +01:00
Copy Link

Removed subscriber: @clouclou-2

Removed subscriber: @clouclou-2
Giuseppe De Marco commented 2015-02-12 11:57:32 +01:00
Copy Link

using

LD_DEBUG=files ./blender  > blender.log 2>&1

activate python console in blender and play autocomplete. Then close blender e read blender.log.
In my case, the compiled from scratch, exposes:

  6357:     calling fini: /home/wert/Progs/blender-2.73a_build/bin/2.73/python/lib/python3.4/lib-dynload/readline.cpython-34m-x86_64-linux-gnu.so [0]
  6357:     
  6357:     
  6357:     calling fini: /lib/x86_64-linux-gnu/libpthread.so.0 [0]
  6357:     
  6357:     
  6357:     calling fini: /lib/x86_64-linux-gnu/libreadline.so.6 [0]

Running it with 2.73a static version

I can see these errors ( uncompatible system-space binary )

6377: opening file=/usr/lib/x86_64-linux-gnu/libSDL.so - [x]; direct_opencount=1
6377:
6377: /usr/lib/x86_64-linux-gnu/libSDL.so: error: symbol lookup error: undefined symbol: SDL_GetPlatform (fatal)
6377: /usr/lib/x86_64-linux-gnu/libSDL.so: error: symbol lookup error: undefined symbol: SDL_memcpy (fatal)
6377: /usr/lib/x86_64-linux-gnu/libSDL.so: error: symbol lookup error: undefined symbol: SDL_calloc (fatal)
6377: /usr/lib/x86_64-linux-gnu/libSDL.so: error: symbol lookup error: undefined symbol: SDL_realloc (fatal)
6377: /usr/lib/x86_64-linux-gnu/libSDL.so: error: symbol lookup error: undefined symbol: SDL_free (fatal)
6377: /usr/lib/x86_64-linux-gnu/libSDL.so: error: symbol lookup error: undefined symbol: SDL_getenv (fatal)
6377: /usr/lib/x86_64-linux-gnu/libSDL.so: error: symbol lookup error: undefined symbol: SDL_setenv (fatal)
6377: /usr/lib/x86_64-linux-gnu/libSDL.so: error: symbol lookup error: undefined symbol: SDL_qsort (fatal)

and then

  6397:     calling fini: /home/wert/Progs/blender-2.73a-linux-glibc211-x86_64/2.73/python/lib/python3.4/lib-dynload/readline.cpython-34m.so [0]
  6397:     
  6397:     
  6397:     calling fini: /lib/x86_64-linux-gnu/libpthread.so.0 [0]
  6397:     
  6397:     
  6397:     calling fini: /lib/x86_64-linux-gnu/libreadline.so.6 [0]

Please do this test and post your results, I'm shure that there will be an incompatibility between static compiled readline.cpython-34m.so and system's libreadline.so.6.

reference:
https://wiki.archlinux.org/index.php/Step-by-step_debugging_guide

using ``` LD_DEBUG=files ./blender > blender.log 2>&1 ``` activate python console in blender and play autocomplete. Then close blender e read blender.log. In my case, the compiled from scratch, exposes: 6357: calling fini: /home/wert/Progs/blender-2.73a_build/bin/2.73/python/lib/python3.4/lib-dynload/readline.cpython-34m-x86_64-linux-gnu.so [0] 6357: 6357: 6357: calling fini: /lib/x86_64-linux-gnu/libpthread.so.0 [0] 6357: 6357: 6357: calling fini: /lib/x86_64-linux-gnu/libreadline.so.6 [0] Running it with 2.73a static version I can see these errors ( uncompatible system-space binary ) 6377: opening file=/usr/lib/x86_64-linux-gnu/libSDL.so - [x]; direct_opencount=1 6377: 6377: /usr/lib/x86_64-linux-gnu/libSDL.so: error: symbol lookup error: undefined symbol: SDL_GetPlatform (fatal) 6377: /usr/lib/x86_64-linux-gnu/libSDL.so: error: symbol lookup error: undefined symbol: SDL_memcpy (fatal) 6377: /usr/lib/x86_64-linux-gnu/libSDL.so: error: symbol lookup error: undefined symbol: SDL_calloc (fatal) 6377: /usr/lib/x86_64-linux-gnu/libSDL.so: error: symbol lookup error: undefined symbol: SDL_realloc (fatal) 6377: /usr/lib/x86_64-linux-gnu/libSDL.so: error: symbol lookup error: undefined symbol: SDL_free (fatal) 6377: /usr/lib/x86_64-linux-gnu/libSDL.so: error: symbol lookup error: undefined symbol: SDL_getenv (fatal) 6377: /usr/lib/x86_64-linux-gnu/libSDL.so: error: symbol lookup error: undefined symbol: SDL_setenv (fatal) 6377: /usr/lib/x86_64-linux-gnu/libSDL.so: error: symbol lookup error: undefined symbol: SDL_qsort (fatal) and then 6397: calling fini: /home/wert/Progs/blender-2.73a-linux-glibc211-x86_64/2.73/python/lib/python3.4/lib-dynload/readline.cpython-34m.so [0] 6397: 6397: 6397: calling fini: /lib/x86_64-linux-gnu/libpthread.so.0 [0] 6397: 6397: 6397: calling fini: /lib/x86_64-linux-gnu/libreadline.so.6 [0] Please do this test and post your results, I'm shure that there will be an incompatibility between static compiled readline.cpython-34m.so and system's libreadline.so.6. reference: https://wiki.archlinux.org/index.php/Step-by-step_debugging_guide
Campbell Barton changed title from Crash during autocompletion in Python Console to Crash during autocompletion in PyConsole (Linux Library Compatibility) 2015-02-12 12:28:20 +01:00
Thomas commented 2015-02-12 23:30:21 +01:00
Copy Link

An easy way to reproduce this error: Download ubuntustudio 14.10, burn iso on a DVD, and boot from DVD in live modus. Blender 2.70a is on the ubuntustudio live DVD and produces this segfault.
Or use virtualbox and boot from the iso file, if you don't want to waste a DVD.

An easy way to reproduce this error: Download ubuntustudio 14.10, burn iso on a DVD, and boot from DVD in live modus. Blender 2.70a is on the ubuntustudio live DVD and produces this segfault. Or use virtualbox and boot from the iso file, if you don't want to waste a DVD.
Giuseppe De Marco commented 2015-02-14 12:01:36 +01:00
Copy Link

Hi Thomas,

on a ubuntu 14.04

Linux qwert-desktop 3.13.0-23-generic #45-Ubuntu SMP Fri Apr 4 06:58:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

with partner this repository + mate repository
it doesn't crash.

I never use the october releases of ubuntu, because it have updates only for 6 month.
For a workstation the LTS releases are always best, more stable and supported.

Hi Thomas, on a ubuntu 14.04 Linux qwert-desktop 3.13.0-23-generic #45-Ubuntu SMP Fri Apr 4 06:58:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux with partner this repository + mate repository it doesn't crash. I never use the october releases of ubuntu, because it have updates only for 6 month. For a workstation the LTS releases are always best, more stable and supported.
3dvits@gmail.com commented 2015-02-14 12:07:18 +01:00
Author
Copy Link

I never use the october releases of ubuntu, because it have updates only for 6 month.
For a workstation the LTS releases are always best, more stable and supported.

Oh, really? We are very happy for you. But the problem, unfortunately, is evident not only in 14.10. And even if so, it is a bug and should be fixed.

>I never use the october releases of ubuntu, because it have updates only for 6 month. >For a workstation the LTS releases are always best, more stable and supported. Oh, really? We are very happy for you. But the problem, unfortunately, is evident not only in 14.10. And even if so, it is a bug and should be fixed.
Thomas commented 2015-02-14 13:15:29 +01:00
Copy Link

Hi Giuseppe,

normally, that's also my philosophy...but since 14.04, I cannot connect to my HP network printer - and I found some hints that the bugfix for this comes with 14.10. It's always a trade off between bug fixes and new bugs :-). The way back to 14.04 would be a complete install from scratch...not really a possibility for me. I tried using an older blender version - but with that, my scenes are looking very strange, cubes are becoming spheres.
Python code completion is not the most important feature for me - but I'm with acvarium, it's a bug and I hope it will be fixed. Does it help if I post the debug output as you proposed?

Hi Giuseppe, normally, that's also my philosophy...but since 14.04, I cannot connect to my HP network printer - and I found some hints that the bugfix for this comes with 14.10. It's always a trade off between bug fixes and new bugs :-). The way back to 14.04 would be a complete install from scratch...not really a possibility for me. I tried using an older blender version - but with that, my scenes are looking very strange, cubes are becoming spheres. Python code completion is not the most important feature for me - but I'm with acvarium, it's a bug and I hope it will be fixed. Does it help if I post the debug output as you proposed?
Kévin Dietrich commented 2015-02-14 13:28:23 +01:00
Member
Copy Link

Removed subscriber: @kevindietrich

Removed subscriber: @kevindietrich
Thomas commented 2015-02-14 14:28:08 +01:00
Copy Link

I started, as you asked me, blender with
LD_DEBUG=files blender > blender.log 2>&1
Because I don't call ./blender, it's the official blender version of ubuntu 14.10.

Here are the last lines before it crashes:

      4598:	file=/usr/lib/python3.4/lib-dynload/readline.cpython-34m-x86_64-linux-gnu.so [0];  dynamically loaded by /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0 [0]
      4598:	file=/usr/lib/python3.4/lib-dynload/readline.cpython-34m-x86_64-linux-gnu.so [0];  generating link map
      4598:	  dynamic: 0x00007fb1697b0d38  base: 0x00007fb1695ab000   size: 0x00000000002074c0
      4598:	    entry: 0x00007fb1695ada90  phdr: 0x00007fb1695ab040  phnum:                  7
      4598:	
      4598:	
      4598:	file=libreadline.so.6 [0];  needed by /usr/lib/python3.4/lib-dynload/readline.cpython-34m-x86_64-linux-gnu.so [0]
      4598:	file=libreadline.so.6 [0];  generating link map
      4598:	  dynamic: 0x00007fb1695a3710  base: 0x00007fb169365000   size: 0x0000000000245ef8
      4598:	    entry: 0x00007fb169377f90  phdr: 0x00007fb169365040  phnum:                  7
      4598:	
      4598:	
      4598:	file=/usr/lib/x86_64-linux-gnu/libedit.so.2 [0];  needed by /lib/x86_64-linux-gnu/libreadline.so.6 [0] (relocation dependency)
      4598:	
      4598:	
      4598:	file=/usr/lib/x86_64-linux-gnu/libedit.so.2 [0];  needed by /usr/lib/python3.4/lib-dynload/readline.cpython-34m-x86_64-linux-gnu.so [0] (relocation dependency)
      4598:	
      4598:	
      4598:	calling init: /lib/x86_64-linux-gnu/libreadline.so.6
      4598:	
      4598:	
      4598:	calling init: /usr/lib/python3.4/lib-dynload/readline.cpython-34m-x86_64-linux-gnu.so
      4598:	
      4598:	opening file=/usr/lib/python3.4/lib-dynload/readline.cpython-34m-x86_64-linux-gnu.so [0]; direct_opencount=1
      4598:	
bind: Invalid command `enable-meta-key'.
Writing: /tmp/blender.crash.txt
      4598:	opening file=/lib/x86_64-linux-gnu/libgcc_s.so.1 [0]; direct_opencount=2
      4598:

Then I renamed the file /usr/lib/python3.4/lib-dynload/readline.cpython-34m-x86_64-linux-gnu.so to force blender to search it somewhere else. Now code completion works without segmentation fault.
I don't know enough about linux shared libraries and the difference between the /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0 and the lib's in /usr/lib/python3.4/lib-dynload/ to understand what's going on.

I started, as you asked me, blender with LD_DEBUG=files blender > blender.log 2>&1 Because I don't call ./blender, it's the official blender version of ubuntu 14.10. Here are the last lines before it crashes: ``` 4598: file=/usr/lib/python3.4/lib-dynload/readline.cpython-34m-x86_64-linux-gnu.so [0]; dynamically loaded by /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0 [0] 4598: file=/usr/lib/python3.4/lib-dynload/readline.cpython-34m-x86_64-linux-gnu.so [0]; generating link map 4598: dynamic: 0x00007fb1697b0d38 base: 0x00007fb1695ab000 size: 0x00000000002074c0 4598: entry: 0x00007fb1695ada90 phdr: 0x00007fb1695ab040 phnum: 7 4598: 4598: 4598: file=libreadline.so.6 [0]; needed by /usr/lib/python3.4/lib-dynload/readline.cpython-34m-x86_64-linux-gnu.so [0] 4598: file=libreadline.so.6 [0]; generating link map 4598: dynamic: 0x00007fb1695a3710 base: 0x00007fb169365000 size: 0x0000000000245ef8 4598: entry: 0x00007fb169377f90 phdr: 0x00007fb169365040 phnum: 7 4598: 4598: 4598: file=/usr/lib/x86_64-linux-gnu/libedit.so.2 [0]; needed by /lib/x86_64-linux-gnu/libreadline.so.6 [0] (relocation dependency) 4598: 4598: 4598: file=/usr/lib/x86_64-linux-gnu/libedit.so.2 [0]; needed by /usr/lib/python3.4/lib-dynload/readline.cpython-34m-x86_64-linux-gnu.so [0] (relocation dependency) 4598: 4598: 4598: calling init: /lib/x86_64-linux-gnu/libreadline.so.6 4598: 4598: 4598: calling init: /usr/lib/python3.4/lib-dynload/readline.cpython-34m-x86_64-linux-gnu.so 4598: 4598: opening file=/usr/lib/python3.4/lib-dynload/readline.cpython-34m-x86_64-linux-gnu.so [0]; direct_opencount=1 4598: bind: Invalid command `enable-meta-key'. Writing: /tmp/blender.crash.txt 4598: opening file=/lib/x86_64-linux-gnu/libgcc_s.so.1 [0]; direct_opencount=2 4598: ``` Then I renamed the file /usr/lib/python3.4/lib-dynload/readline.cpython-34m-x86_64-linux-gnu.so to force blender to search it somewhere else. Now code completion works without segmentation fault. I don't know enough about linux shared libraries and the difference between the /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0 and the lib's in /usr/lib/python3.4/lib-dynload/ to understand what's going on.
Giuseppe De Marco commented 2015-02-14 15:32:26 +01:00
Copy Link

Nice workaround Thomas,
If I understood the bug, in your case, this affects the ubuntu blender package, so the ubuntu mantainers should recompile it with the readline actually distribuited with 14.10.

If the problem is this, this bug should be closed because it doesn't affects official blender package, isn't so ?

Nice workaround Thomas, If I understood the bug, in your case, this affects the ubuntu blender package, so the ubuntu mantainers should recompile it with the readline actually distribuited with 14.10. If the problem is this, this bug should be closed because it doesn't affects official blender package, isn't so ?
Thomas commented 2015-02-14 16:39:40 +01:00
Copy Link

I'm not sure if a recompile solves the problem, because the bug in my case affects the ubuntu version, an official build from blender.org, and even a recompiled version (see my earlier posts). Maybe a recompile on a fresh ubuntu 14.10 solves the problem.
I guess it's not a blender bug. But I'm only a blender user, not a developer, and I don't know if this problem is worth investigating much more effort to find the cause.

I'm not sure if a recompile solves the problem, because the bug in my case affects the ubuntu version, an official build from blender.org, and even a recompiled version (see my earlier posts). Maybe a recompile on a fresh ubuntu 14.10 solves the problem. I guess it's not a blender bug. But I'm only a blender user, not a developer, and I don't know if this problem is worth investigating much more effort to find the cause.
Thomas commented 2015-02-14 16:50:53 +01:00
Copy Link

Ah, there are more problems in the ubuntu 14.10 version. I continued working on a scene, and when I tried to move some objects to another layer (m), blender crashed when a clicked on the target layer symbol. This also occurs on a fresh ubuntustudio installation, I tried it with the ubuntustudio live session.
I'll try to contact the ubuntu maintainers - don't know how, but I think google will help.

Ah, there are more problems in the ubuntu 14.10 version. I continued working on a scene, and when I tried to move some objects to another layer (m), blender crashed when a clicked on the target layer symbol. This also occurs on a fresh ubuntustudio installation, I tried it with the ubuntustudio live session. I'll try to contact the ubuntu maintainers - don't know how, but I think google will help.
Giuseppe De Marco commented 2015-02-14 17:15:23 +01:00
Copy Link

If you are looking for a workaround for you, you can do a chroot of a ubuntu 14.04 or debian inside your 14.10. With chroot you should use CUDA as well.

http://www.binarytides.com/setup-chroot-ubuntu-debootstrap/

As we have considered this ticket we should close this bug because it doesn't affects directly blender but specific distributions packages.

If you are looking for a workaround for you, you can do a chroot of a ubuntu 14.04 or debian inside your 14.10. With chroot you should use CUDA as well. http://www.binarytides.com/setup-chroot-ubuntu-debootstrap/ As we have considered this ticket we should close this bug because it doesn't affects directly blender but specific distributions packages.
Giuseppe De Marco commented 2015-02-14 17:15:48 +01:00
Copy Link

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Thomas commented 2015-02-14 17:22:50 +01:00
Copy Link

Hi everybody, I submitted an ubuntu bug report: blender crashes on python code completion

Hi everybody, I submitted an ubuntu bug report: [blender crashes on python code completion ](https://bugs.launchpad.net/ubuntu/+source/blender/+bug/1421977)
Xavier Thomas commented 2015-02-24 15:44:22 +01:00
Member
Copy Link

Added subscriber: @XavierThomas

Added subscriber: @XavierThomas
Xavier Thomas commented 2015-02-24 15:44:22 +01:00
Member
Copy Link

Hi,

I am suffering from this bug also. I am using Debian testing and none of the workarounds is working for me.

I tried recompiling blender with and without PYTHON_INSTALL but nothing changes. The catch that make me thinks this might be a Blender (build system) bug instead of a system bug is that I can do auto-completion using readline in pretty much any python console except Blender's:

import rlcompleter, readline
readline.parse_and_bind('tab:complete')

Works in the CPython's console but crash at "import readline" in Blender's console.

Hi, I am suffering from this bug also. I am using Debian testing and none of the workarounds is working for me. I tried recompiling blender with and without PYTHON_INSTALL but nothing changes. The catch that make me thinks this might be a Blender (build system) bug instead of a system bug is that I can do auto-completion using readline in pretty much any python console except Blender's: import rlcompleter, readline readline.parse_and_bind('tab:complete') Works in the CPython's console but crash at "import readline" in Blender's console.
Giuseppe De Marco commented 2015-02-25 09:39:11 +01:00
Copy Link

Xavier blender python autocompletion binds libreadline present on your system,

please follow the solution proposed by Thomas, rename the blender local lib.
read the previous comments

Xavier blender python autocompletion binds libreadline present on your system, please follow the solution proposed by Thomas, rename the blender local lib. read the previous comments
Xavier Thomas commented 2015-02-25 13:46:32 +01:00
Member
Copy Link

Giuseppe,

I did try renaming but it did not work yesterday. Today I retried after compiling with PYTHON_INSTALL deactivated in CMake and renaming /usr/lib/python3.4/lib-dynload/readline.cpython-34m-x86_64-linux-gnu.so and it works. Thanks

Giuseppe, I did try renaming but it did not work yesterday. Today I retried after compiling with PYTHON_INSTALL deactivated in CMake and renaming /usr/lib/python3.4/lib-dynload/readline.cpython-34m-x86_64-linux-gnu.so and it works. Thanks
Campbell Barton commented 2015-02-26 03:21:08 +01:00
Owner
Copy Link

Found the cause of the issue, and it is indeed a configuration problem. (not an error in our code).

There are 2 libraries that support the 'readline' API (libreadline and libedit), however they aren't 100% API compatible (if they were, we wouldn't have any crashes).

A quick way to test the crash is:

  blender --python-console

Where this works:

  blender --python-console --background

Whats happening is LLVM is linked with libedit, loading Blender's GUI, loads OpenGL, On some systems this will use LLVM, which loads libedit.

Afterwards, when Python attempts to import readline, it uses the symbols for libedit which has an incompatible rl_startup_hook, that is called immediately, (before Python's module has been initialized) and crashes, whereas libreadline postpones executing the callback.

So this fix is to ensure libedit is never used by Python's readline module.

Incidentally, Python is aware of the differences and has ifdef's to support libedit, however these are only enabled when __APPLE__ is defined, building Python against libedit on Linux is possible, but better solve by using correct linking.

Found the cause of the issue, and it is indeed a configuration problem. (not an error in our code). There are 2 libraries that support the 'readline' API (libreadline and libedit), however they aren't 100% API compatible *(if they were, we wouldn't have any crashes)*. A quick way to test the crash is: ``` blender --python-console ``` Where this works: ``` blender --python-console --background ``` Whats happening is LLVM is linked with `libedit`, loading Blender's GUI, loads OpenGL, On *some* systems this will use LLVM, which loads `libedit`. Afterwards, when Python attempts to import `readline`, it uses the symbols for `libedit` which has an incompatible `rl_startup_hook`, that is called immediately, (before Python's module has been initialized) and crashes, whereas `libreadline` postpones executing the callback. So this fix is to ensure `libedit` is never used by Python's `readline` module. ---- Incidentally, Python is aware of the differences and has ifdef's to support `libedit`, however these are only enabled when `__APPLE__` is defined, building Python against `libedit` on Linux is possible, but better solve by using correct linking.
Campbell Barton commented 2015-02-26 09:22:33 +01:00
Owner
Copy Link

Changed status from 'Archived' to: 'Open'

Changed status from 'Archived' to: 'Open'
Campbell Barton commented 2015-02-26 12:57:06 +01:00
Owner
Copy Link

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Campbell Barton commented 2015-02-26 12:57:06 +01:00
Owner
Copy Link

Committed workaround f159ed7746

This spesific crash is fixed, however the error with readline crashing on load isnt.
That really needs to be fixed by linking Blender differently, since not all Linux distro's suffer this problem, it should be possible to resolve.

Committed workaround f159ed7746 This spesific crash is fixed, however the error with `readline` crashing on load isnt. That really needs to be fixed by linking Blender differently, since not all Linux distro's suffer this problem, it should be possible to resolve.
Xavier Thomas commented 2015-02-26 13:13:31 +01:00
Member
Copy Link

Hi Campbell,

Nice job spotting the origin of the bug. This all make sense now: the bug appeared for me after nvidia stopped supporting my gpu and I had to switch to nouveau.

Hi Campbell, Nice job spotting the origin of the bug. This all make sense now: the bug appeared for me after nvidia stopped supporting my gpu and I had to switch to nouveau.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
Asset datablocks, libraries, browser and shelf
Interest
Audio
Interest
Automated Testing
Interest
BlendFile
Interest
Blender Asset Bundle
Interest
Code Documentation
Code comments, Python/RNA API descriptions
Interest
Collada
Interest
Compatibility
Backward and forward compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
FBX
FBX I/O related topics
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
USD
Interest
UV Editing
Interest
Undo
Interest
User Interface
Interest
VFX & Video
Interest
Video Sequencer
Interest
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Wayland windowing on Unix
Interest
Workbench
Interest
glTF
glTF format I/O topics
Interest: X11
Xorg/X11 windowing
Legacy
Asset Browser Project
Archived
Legacy
Blender 2.8 Project
Archived
Legacy
Milestone 1: Basic, Local Asset Browser
Archived
Legacy
OpenGL Error
Archived
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Related to security, see policy: https://developer.blender.org/docs/handbook/bug_reports/vulnerability_reports/
Module
Animation & Rigging
Module
Asset System
Module
Core
Module
Development Management
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
Windows
Platform
macOS
Severity
High
Severity
Low
Severity
Normal
Severity
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Archived
Type
Report
Archived
Type
To Do
No Label
Module
Platforms, Builds & Tests
Platform
Linux
Severity
Normal
Status
Resolved
Type
Report
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Hoshinova James-McCarthy-4 Sebastian-Herholz casey-bianco-davis gandalf3 Blendify Aaron Carlisle quantimoney Aditya Y Jeppu Alaska Alaska angavrilov Alexander Gavrilov frogstomp Aleš Jelovčan amelief Amélie Fondevilla elubie Andrea Weikert Andy_Goralczyk Andy Goralczyk ankitm Ankit Meel Anthony-Roberts Anthony Roberts antoniov Antonio Vazquez aras_p Aras Pranckevicius Arnd Arnd Marijnissen bartvdbraak Bart van der Braak mont29 Bastien Montagne blender-bot Blender Bot bnagirniak Bogdan Nagirniak BClark Brad Clark brecht Brecht Van Lommel BrianSavery Brian Savery (AMD) ideasman42 Campbell Barton CharlesWardlaw Charles Wardlaw CharlieJolly Charlie Jolly Chris_Blackbourn Chris Blackbourn lateasusual Chris Clyne (Lateasusual) ChrisLend Christoph Lendenfeld HobbesOS Cian Jinks fclem Clément Foucault cmbasnett Colin Basnett Kdaf Colin Marmond dfelinto Dalai Felinto pioverfour Damien Picard DanielBystedt Daniel Bystedt pepe-school-land Daniel Martinez Lara zanqdo Daniel Salazar Mets Demeter Dzadik erik85 Erik Abrahamsson EAW Evan Wilson filedescriptor Falk David fsiddi Francesco Siddi GaiaClary Gaia Clary DagerD Georgiy Markelov mano-wii Germano Cavalcante zazizizou Habib Gahbiche HooglyBoogly Hans Goudey Harley Harley Acheson weasel Henrik D. Hjalti Hjalti Hjálmarsson howardt Howard Trickey nirved-1 Hristo Gueorguiev mod_moder Iliya Katushenock brita Inês Almeida JacquesLucke Jacques Lucke Jason-Fielder Jason Fielder JasonSchleifer Jason schleifer Jebbly Jeffrey Liu Jeroen-Bakker Jeroen Bakker deadpin Jesse Yurkovich neXyon Joerg Mueller eliphaz John Kiril Swenson guitargeek Johnny Matthews Brainzman Jonas Holzman JoniMercado Jonatan Mercado JorgeBernalMartinez Jorge Bernal JosephEagar Joseph Eagar JoshuaLeung Joshua Leung Bone-Studio Juan Gea jpbouza-4 Juan Pablo Bouza JulianEisel Julian Eisel JulienDuroure Julien Duroure JulienKaspar Julien Kaspar kevindietrich Kévin Dietrich lone_noel Leon Schittek LucianoMunoz Luciano Muñoz Sessarego LukasStockner Lukas Stockner LukasTonne Lukas Tönne LunaRood Luna Rood MaiLavelle Mai Lavelle EosFoxx Marion Stalke Baardaap Martijn Versteegh scorpion81 Martin Felke mendio Matias Mendiola Matt-McLin Matt McLin MetinSeven Metin Seven wave Michael B Johnson Michael-Jones Michael Jones (Apple) makowalski Michael Kowalski pragma37 Miguel Pozo nrupsis Nate Rupsis jesterking Nathan Letwory nathanvegdahl Nathan Vegdahl PrototypeNM1 Nicholas Rishel nickberckley Nika Kutsniashvili Sirgienko Nikita Sirgienko OmarEmaraDev Omar Emara pablovazquez Pablo Vazquez PaoloAcampora Paolo Acampora PascalSchon Pascal Schön pmoursnv Patrick Mours muxed-reality Peter Kim lichtwerk Philipp Oeser P2design Pierrick PICAUT PratikPB2123 Pratik Borhade Limarest Ramil Roosileht farsthary Raul Fernandez Hernandez LazyDodo Ray molenkamp iss Richard Antalik rjg Robert Guetzkow salipour Sahar A. Kashi Sayak-Biswas Sayak Biswas Sean-Kim Sean Kim sherholz Sebastian Herholz sebastian_k Sebastian Koenig ZedDB Sebastian Parborg sebbas Sebastián Barschkis Sergey Sergey Sharybin IRIEShinsuke Shinsuke Irie sidd017 Siddhartha Jejurkar SietseB Sietse Brouwer SimonThommes Simon Thommes SonnyCampbell_Unity Sonny Campbell Stefan_Werner Stefan Werner Lockal Sv. Lockal dr.sybren Sybren A. Stüvel ThomasDinges Thomas Dinges Ton Ton Roosendaal BassamKurdali Ursula kurdali Vasyl-Pidhirskyi Vasyl Pidhirskyi WannesMalfait Wannes Malfait wbmoss_dev Wayde Moss weizhen Weizhen Huang leesonw William Leeson xavierh Xavier Hallade jenkm Yevgeny Makarov ChengduLittleA YimingWu gfxcoder jon denning
No Assignees Giuseppe De Marco
9 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: blender/blender#43491
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?