Red Hat Bugzilla – Bug 971250
[abrt] blender-2.67a-1.fc18: generic_run_one: Process /usr/bin/blender was killed by signal 11 (SIGSEGV)
Last modified: 2013-08-31 19:58:07 EDT
Description of problem: To reproduce (at least on my laptop): * open some big scene with much polygons in blender * then enter edit mode with some complex object * and then switching projection (Num 5 button) causes blender to crash Version-Release number of selected component: blender-2.67a-1.fc18 Additional info: reporter: libreport-2.1.4 backtrace_rating: 4 cmdline: blender core_backtrace: crash_function: generic_run_one executable: /usr/bin/blender kernel: 3.9.4-200.fc18.x86_64 runlevel: N 5 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #1 generic_run_one at translate/translate_generic.c:646 #2 generic_run at translate/translate_generic.c:733 #3 u_vbuf_translate_buffers at util/u_vbuf.c:428 #4 u_vbuf_translate_begin at util/u_vbuf.c:599 #5 u_vbuf_draw_vbo at util/u_vbuf.c:1194 #6 st_draw_vbo at ../../src/mesa/state_tracker/st_draw.c:286 #7 vbo_draw_arrays at ../../src/mesa/vbo/vbo_exec_array.c:624 #8 drawgrid_draw at /usr/src/debug/blender-2.67a/source/blender/editors/space_view3d/view3d_draw.c:260 #9 view3d_main_area_draw at /usr/src/debug/blender-2.67a/source/blender/editors/space_view3d/view3d_draw.c:411 #10 ED_region_do_draw at /usr/src/debug/blender-2.67a/source/blender/editors/screen/area.c:432 Potential duplicate: bug 962782
Created attachment 757478 [details] File: backtrace
Created attachment 757479 [details] File: cgroup
Created attachment 757480 [details] File: dso_list
Created attachment 757481 [details] File: environ
Created attachment 757482 [details] File: limits
Created attachment 757483 [details] File: maps
Created attachment 757484 [details] File: open_fds
Created attachment 757485 [details] File: proc_pid_status
Created attachment 757486 [details] File: var_log_messages
Created attachment 757487 [details] File: xsession_errors
Tried also blender 2.67b (compiled from source by editing 2.67a spec file) and blender 2.64, got more crashes. I can post backtraces if needed.
EDIT: To reproduce the bug you need to start switching projections (ortho/persp) when some of common views choosen (side/front/back/top etc). So just open blender press Num3, then press Num5 and see if it crashes.
Downgrading mesa-dri-drivers (firstly I downloaded mesa-dri-filesystem-9.0.1 x86_64 and i686 from rpmfind.net and installed them with rpm -i --nodeps) (I did sudo yum downgrade mesa-dri-drivers mesa-dri-filesystem mesa-libxatracker{,-devel} llvm-libs) Should I create bug "mesa-dri-drivers-9.2.0 blender crash" or maybe report to mesa bugtracker?
forgot to say, the problem was in mesa-dri-drivers-9.2-0.7.20130528.fc18
There is a closed bug: 962782 that seems to support it being a mesa issue. It would be much appreciated if whatever magic needs to happen could get into some sort of bug fix for fc18.
FWIW I downloaded http://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/source/SRPMS/m/mesa-9.2-0.12.20130610.fc20.src.rpm built it and replaced all of the mesa-* packages on my system with those from the built binaries. As suggested in 962782 this resolved the problem with Blender.
Trying to get Blender 2.67 to change to quad view, via shortcut keys or by menu command. reporter: libreport-2.1.4 backtrace_rating: 4 cmdline: blender crash_function: generic_run_one executable: /usr/bin/blender kernel: 3.9.6-200.fc18.x86_64 package: blender-2.67a-2.fc18 reason: Process /usr/bin/blender was killed by signal 11 (SIGSEGV) reported_to: uReport: BTHASH=405f90bc2d92b4344d3ed7c2dc7495b77dd1f777 runlevel: N 5 uid: 1000
So would mesa-dri-drivers be updated in fedora-18? Do I miss something that blocks this workaround?
See: http://wiki.blender.org/index.php/Doc:2.6/Manual/Your_First_Animation/1.A_static_Gingerbread_Man "With Num lock activated, change to the front view with 1 NumPad and to orthogonal view with 5 NumPad." When selecting orthogonal view, Blender crashes. reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: blender crash_function: generic_run_one executable: /usr/bin/blender kernel: 3.10.9-100.fc18.x86_64 package: blender-2.68a-1.fc18 reason: Process /usr/bin/blender was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 1001
For the record, I managed to reproduce this bug with Blender 2.68a and mesa-9.2-0.7.20130528 on Fedora 18. Updating mesa to mesa-9.2-0.12.20130610 from koji: http://koji.fedoraproject.org/koji/buildinfo?buildID=432070 fixes it. => switching component to mesa. Adam, Dave, could you please publish mesa-9.2-0.12.20130610.fc18 to updates-testing?
mesa-9.2-0.12.20130610.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/mesa-9.2-0.12.20130610.fc18
*** Bug 974987 has been marked as a duplicate of this bug. ***
Package mesa-9.2-0.12.20130610.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing mesa-9.2-0.12.20130610.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-15352/mesa-9.2-0.12.20130610.fc18 then log in and leave karma (feedback).
@Vitaly: could you confirm the crash is fixed after the fix in comment 23?
@François Cami: Sorry, currently I don't have Fedora 18 on any of my systems. Try to ask sylvie.andre44 and Charles to confirm the fix.
mesa-9.2-0.12.20130610.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.