Red Hat Bugzilla – Bug 1018531
SIGSEGV when selecting polygons with i915 (libdricore9.2.0.so)
Last modified: 2015-02-18 06:36:04 EST
Description of problem:
Softimage crashes anytime a polygon is selected. The same behavior didn't happen when tested on other laptops with other drivers.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Just selecting any polygon.
Polygon selection shouldn't crash an application.
Stepping through gdb produced this;
Program received signal SIGSEGV, Segmentation fault.
0x00007fff9a15e284 in run_vp (ctx=0x109aea00, stage=<optimized out>) at ../../../src/mesa/tnl/t_vb_program.c:369
369 COPY_CLEAN_4V(machine->VertAttribs[attr], size, data);
Could you attach sample program and mesa version ?
$ rpm -qa mesa
Here's the output;
$ rpm -qa | grep mesa
I googled about the crash and the same type of crash (vbo polygon selection) happened to Blender 3D before (mesa 9.0). I guess this is another use case of vbo selection that wasn't tested at the time? The crash didn't happen with proprietary drivers of both AMD and NVIDIA so I I guess it cancels out the problem with the software.
(In reply to Joe AbdHalim from comment #3)
> I googled about the crash and the same type of crash (vbo polygon selection)
> happened to Blender 3D before (mesa 9.0). I guess this is another use case
> of vbo selection that wasn't tested at the time? The crash didn't happen
> with proprietary drivers of both AMD and NVIDIA so I I guess it cancels out
> the problem with the software.
Attach source of you sample. I will some test it and send bugreport to upstream w/ more info.
I'm sorry the application is a closed source commercial product from Autodesk.
How can I proceed to get this checked? The application was running fine with NVIDIA and AMD's proprietary drivers so I guess the application can be ruled out as the main culprit?
(In reply to Joe AbdHalim from comment #5)
> I'm sorry the application is a closed source commercial product from
> How can I proceed to get this checked? The application was running fine with
> NVIDIA and AMD's proprietary drivers so I guess the application can be ruled
> out as the main culprit?
We can't test proprietary products, but I'm filling bug to upstream.
Ah. I see that you filled..
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
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.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 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 change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.