[Bug 58833] New: [945GME DRI] firefox drops core at startup with DRI enabled

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Dec 28 09:18:34 PST 2012


https://bugs.freedesktop.org/show_bug.cgi?id=58833

          Priority: medium
            Bug ID: 58833
          Assignee: intel-gfx-bugs at lists.freedesktop.org
           Summary: [945GME DRI] firefox drops core at startup with DRI
                    enabled
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: OpenBSD
          Reporter: mrw at eandem.co.uk
          Hardware: x86 (IA32)
            Status: NEW
           Version: XOrg CVS
         Component: DRM/Intel
           Product: DRI

Created attachment 72224
  --> https://bugs.freedesktop.org/attachment.cgi?id=72224&action=edit
gdb bt, Xorg log, dmesg, and working xorg.conf

Bug description:
Each time firefox is started it results in a firefox.core file in the home
directory. firefox does continue to startup without any more issues. From a gdb
backtrace it appears to be a problem in a call to driCreateScreen().  Disabling
DRI in an xorg.conf stops firefox creating a core at startup - originally I was
not using an xorg.conf so the server configured itself.

System environment:
-- chipset: 82945GME 
-- system architecture: i386
-- xf86-video-intel: 2.12.0
-- xserver: X.Org 7.7 X Server 1.12.2
-- mesa: 7.10.3
-- libdrm: whatever is in OBSD release, sorry.
-- kernel: OpenBSD 5.2 release
-- Linux distribution: OpenBSD
-- Machine or mobo model: Acer Aspire One
-- Display connector:

Reproducing steps:
Start firefox and check home directory when it has finally started.

Additional info:
Use non-root account to reproduce since root does not produce cores by default.

The attachment contains
o a gdb backtrace of a firefox core showing the crash in driCreateScreen()
o The Xorg log for the server which produces a core
o System dmesg
o xorg.conf that stops firefox dumping a core.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20121228/9205a3e9/attachment-0001.html>


More information about the intel-gfx-bugs mailing list