Summary: | [865g] webgl enabled pages crash Firefox and mesa | ||
---|---|---|---|
Product: | Mesa | Reporter: | Sandy Beach <dune97> |
Component: | Drivers/DRI/i830 | Assignee: | Default DRI bug account <dri-devel> |
Status: | RESOLVED NOTOURBUG | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | celeonar, eugeni, john_a_s2004, kibi |
Version: | 7.11 | ||
Hardware: | x86 (IA32) | ||
OS: | Linux (All) | ||
URL: | https://bugzilla.mozilla.org/show_bug.cgi?id=699181 | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
dmesg
Xorg log |
Description
Sandy Beach
2011-11-04 22:21:41 UTC
Created attachment 53165 [details]
dmesg
Created attachment 53166 [details]
Xorg log
(In reply to comment #0) > Using an intel i865g GPU 16Mb ddr3200 shared memory -see(1) > mesa and firefox crash when loading webgl page such as <about:support> or > getwebgl.org > > stderr msg:Mesa 7.11 implementation error: unexpected format in > _mesa_choose_tex_format() > Mesa 7.11 implementation error: unexpected MESA_FORMAT for renderbuffer Looks like the bug refers to gen2 Intel graphics: i have an i855 and i'm experiencing the same problem since some Firefox version. Here is the bug i've filed to Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652941 I'm using Debian Sid, Iceweasel 9.0, Mesa 7.11.2. Cesare. I believe this was a firefox issue that mozilla devel has fixed. The crash has not shown up on any of my newer Debian installations with firefox10 and beyond. I can still trigger the crash on an 5 year old debian installation. But after adding a new user to the 5 year old debian installation the crash disappears for the new user. I tested using firefox versions 8, 9, 10, 11 and 13 with the same results for each version. Firefox url = about:support crashes when called by the 5 year old user and firefox url = about:support displays all fields of the about:support webgl page when called by the newly added user. Will, have you already upgraded to Mesa 8 from experimental? The problem is not resolved for me (i855) and i do not reopen this bug only because your bug is specific to Drivers/DRI/i830. I've renamed my mozilla profile and then created a fresh new user as you suggested: Firefox still crashes with about:support and other sites with the same Mesa error you reported. This Mozilla bug seems to prove that there is an Intel/Mesa bug somewhere: https://bugzilla.mozilla.org/show_bug.cgi?id=696636 I haven't yet found the time to file a new bug to Mesa, as they suggested, but i will do. I'm scared to upgrade to Mesa 8, because reading gen2 upstream changelogs entry i suspect i'll have more breakage, since it talks about features removed... Cesare. > I haven't yet found the time to file a new bug to Mesa, as they suggested, but i will do. I'm scared to upgrade to Mesa 8, because reading gen2 upstream
> changelogs entry i suspect i'll have more breakage, since it talks about features removed...
You don't have to upgrade mesa entirely just for this testing. You can compile and install it into any other directory (for example, with ./configure --prefix=/home/myuser/mesa; make; make install), and then use 'export LD_LIBRARY_PATH=/home/myuser/mesa/lib' to tell applications to use this mesa version for testing.
This way, you'll still have your old mesa around in case 8.0.x is broken for you..
I tried to follow the instructions to build Mesa 8.0.1, but when I ran ./configure it reported: configure: error: Direct rendering requires libdrm >= 2.4.24 I've tried re-installing with 'yum reinstall libdrm': Running Transaction Installing : libdrm-2.4.30-1.fc16.i686 1/1 Installed: libdrm.i686 0:2.4.30-1.fc16 but still no further with ./configure, any advice please? With the latest Firefox from Debian (Iceweasel 10.0.3esr-1), the problem looks resolved: no more crashes for me. The fix is documented here: https://bugzilla.mozilla.org/show_bug.cgi?id=696636 https://bugzilla.mozilla.org/show_bug.cgi?id=728656 And for the record, no problems with Mesa 8. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.