Bug 783830 - Segmentation fault of blender when multiple selections
Summary: Segmentation fault of blender when multiple selections
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: blender
Version: 16
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Jochen Schmitt
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-22 16:28 UTC by savaryju
Modified: 2013-02-13 15:06 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 15:06:48 UTC
Type: ---


Attachments (Terms of Use)

Description savaryju 2012-01-22 16:28:14 UTC
Description of problem:

When selecting objects, blender terminate on segfault.
It happens when selecting many objects in one time or one object/one action many times. It can happen just after have loaded the file worked on, or 20 minutes after. 


Version-Release number of selected component (if applicable):

# rpm -qa blender
blender-2.59-3.fc16.x86_64

How reproducible:

Each time I try to work.

Steps to Reproduce:
1.load file
2.select items until it segfaults

Binary from blender.org (2.61) seems to show the same default (see Additional info).

Actual results:


Expected results:


Additional info:

$ gdb blender
GNU gdb (GDB) Fedora (7.3.50.20110722-10.fc16)
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/blender...Reading symbols from /usr/lib/debug/usr/bin/blender.debug...done.
done.
(gdb) run
Starting program: /usr/bin/blender
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7ffff733b700 (LWP 2588)]
[New Thread 0x7ffff2b39700 (LWP 2589)]
[Thread 0x7ffff2b39700 (LWP 2589) exited]
read blend: /home/kj/carriole/carriole/carriole_2011-10-25-11.blend

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff0099e9f in ?? ()
(gdb) bt
#0  0x00007ffff0099e9f in ?? ()
#1  0x00000000ba6b06e8 in ?? ()
#2  0x0000000000000000 in ?? ()
(gdb) py-bt
Traceback (most recent call first):
(gdb) down
Bottom (innermost) frame selected; you cannot go down.
(gdb) up
#1  0x00000000ba6b06e8 in ?? ()




Same try, with blender from blender.org (2.61)

~/blender/blender-2.61-linux-glibc27-x86_64$ gdb ./blender
GNU gdb (GDB) Fedora (7.3.50.20110722-10.fc16)
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /home/kj/blender/blender-2.61-linux-glibc27-x86_64/blender...(no debugging symbols found)...done.
(gdb) run
Starting program: /home/kj/blender/blender-2.61-linux-glibc27-x86_64/blender
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
connect failed: No such file or directory
ndof: spacenavd not found
[New Thread 0x7ffff6bff700 (LWP 2773)]
[Thread 0x7ffff6bff700 (LWP 2773) exited]
[New Thread 0x7ffff6bff700 (LWP 2774)]
AL lib: pulseaudio.c:430: Failed to find format for channel map:
    front-left,front-right,rear-left,rear-right,lfe
[New Thread 0x7ffff17ff700 (LWP 2775)]
[New Thread 0x7ffff07ff700 (LWP 2776)]
[Thread 0x7ffff07ff700 (LWP 2776) exited]
found bundled python: /home/kj/blender/blender-2.61-linux-glibc27-x86_64/2.61/python
[New Thread 0x7fffe5bff700 (LWP 2777)]
[New Thread 0x7fffe4bff700 (LWP 2778)]
[New Thread 0x7fffe43fe700 (LWP 2779)]
[New Thread 0x7fffe33ff700 (LWP 2780)]
[New Thread 0x7fffe23ff700 (LWP 2781)]
[Thread 0x7fffe43fe700 (LWP 2779) exited]
[Thread 0x7fffe33ff700 (LWP 2780) exited]
[New Thread 0x7fffe43fe700 (LWP 2782)]
[New Thread 0x7fffe33ff700 (LWP 2783)]
[Thread 0x7fffe4bff700 (LWP 2778) exited]
[Thread 0x7fffe33ff700 (LWP 2783) exited]
[Thread 0x7fffe43fe700 (LWP 2782) exited]
[Thread 0x7fffe23ff700 (LWP 2781) exited]
[New Thread 0x7fffe23ff700 (LWP 2784)]
[New Thread 0x7fffe33ff700 (LWP 2785)]
[Thread 0x7fffe33ff700 (LWP 2785) exited]
[Thread 0x7fffe23ff700 (LWP 2784) exited]
[Thread 0x7fffe5bff700 (LWP 2777) exited]
read blend: /home/kj/carriole/carriole/carriole_2011-10-25-11_B2.61.blend

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7d1de9f in ?? ()

Comment 1 Fedora End Of Life 2013-01-16 14:06:55 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Fedora End Of Life 2013-02-13 15:06:50 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.