From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 40423] New: Firefox GLX test crashes with Mesa 7.12-devel, Gallium 0.4 on AMD JUNIPER
Date: Sat, 27 Aug 2011 11:21:33 -0700 (PDT) [thread overview]
Message-ID: <bug-40423-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=40423
Summary: Firefox GLX test crashes with Mesa 7.12-devel, Gallium
0.4 on AMD JUNIPER
Product: Mesa
Version: unspecified
Platform: Other
URL: https://crash-stats.mozilla.com/report/index/4a1da9e3-
fef3-4ce6-be03-ce07d2110827
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/Radeon
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: bjacob@mozilla.com
Just got this Firefox crash report:
https://crash-stats.mozilla.com/report/index/4a1da9e3-fef3-4ce6-be03-ce07d2110827
The Firefox crash itself is not relevant to Mesa/ATI, but this report also says
(look at App Notes) that the little GLX test process that Firefox runs at
startup also crashed:
App Notes
GLXtest process failed (received signal 11):
VENDOR
X.Org
RENDERER
Gallium 0.4 on AMD JUNIPER
VERSION
2.1 Mesa 7.12-devel (git-5379a70)
TFP
TRUE
You can find the source code of this test here:
http://hg.mozilla.org/mozilla-central/file/d0700ba932b4/toolkit/xre/glxtest.cpp#l107
It's even simpler than 'glxinfo' but differs in that it uses a GLX pixmap
instead of a XWindow to back the GL context.
As the 'App Notes' say, this process crashed on signal 11 (segmentation fault)
In the crash report, by clicking the Modules tab you can get version info for
the libraries loaded in the Firefox process. For example:
libX11.so.6.3.0
libGL.so.1.2
Unfortunately I don't have any more information about it: no stack, no more
device information.
Note that Firefox itself is "fine", the present bug is only making the GLX test
process crash, Firefox notices that and as a result disables GL-dependent
features. But it would be nice to not have to disable these features ;-)
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-08-27 18:21 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-27 18:21 bugzilla-daemon [this message]
2011-08-27 18:22 ` [Bug 40423] Firefox GLX test crashes with Mesa 7.12-devel, Gallium 0.4 on AMD JUNIPER bugzilla-daemon
2011-08-27 18:24 ` bugzilla-daemon
2011-08-29 18:04 ` bugzilla-daemon
2011-08-29 18:31 ` bugzilla-daemon
2011-08-29 18:31 ` bugzilla-daemon
2011-08-29 22:43 ` bugzilla-daemon
2011-08-30 20:55 ` bugzilla-daemon
2011-08-30 20:56 ` bugzilla-daemon
2011-08-30 21:00 ` bugzilla-daemon
2011-08-30 21:12 ` bugzilla-daemon
2011-08-30 21:33 ` bugzilla-daemon
2011-08-30 21:36 ` bugzilla-daemon
2011-08-30 21:55 ` bugzilla-daemon
2011-09-01 12:10 ` bugzilla-daemon
2011-09-01 12:29 ` bugzilla-daemon
2011-09-24 11:43 ` bugzilla-daemon
2011-09-25 16:18 ` bugzilla-daemon
2011-09-25 16:20 ` bugzilla-daemon
2011-09-29 11:07 ` bugzilla-daemon
2011-09-29 13:25 ` bugzilla-daemon
2011-10-01 3:45 ` bugzilla-daemon
2011-10-01 4:08 ` bugzilla-daemon
2011-10-01 4:22 ` bugzilla-daemon
2011-10-01 23:59 ` bugzilla-daemon
2011-10-06 11:54 ` bugzilla-daemon
2011-12-29 17:16 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-40423-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.