708180 - crash on rendering webgl content

Status: RESOLVED INCOMPLETE

(Core :: Graphics: CanvasWebGL, defect)

Description

[Govardhana]

User Agent: Mozilla/5.0 (Ubuntu; X11; Linux i686; rv:9.0) Gecko/20100101 Firefox/9.0
Build ID: 20111124194641

Steps to reproduce:

installed mesa package in linux for webgl rendering to using driver support .....
 when a webgl renders either firefox don't renders or crashes....


Actual results:

OpenGL: Tungsten Graphics, Inc -- Mesa DRI Intel(R) Ironlake Mobile x86/MMX/SSE2 -- 1.4 (2.1 Mesa 7.12-devel (git-c87d1a3 natty-oibaf-ppa)) -- texture_from_pixmap
WebGL? libGL.so.1? libGL.so.1+
GL Context? GL Context+
X_GLXRender: GLXBadRenderRequest; 2 requests agoxpcom_runtime_abort(###!!! ABORT: X_GLXRender: GLXBadRenderRequest; 2 requests ago: file /build/buildd/firefox-9.0~b3+build1/build-tree/mozilla/toolkit/xre/nsX11ErrorHandler.cpp, line 199)


Expected results:

webgl content shd be rendering.....

Comment 1

[Govardhana]

do i have alternative way to fix web-gl rendering .................

when i type about:support in url .... the following table i got details about graphics.....


Adapter DescriptionTungsten Graphics, Inc -- Mesa DRI Intel(R) Ironlake Mobile x86/MMX/SSE2

Driver Version1.4 (2.1 Mesa 7.12-devel (git-c87d1a3 natty-oibaf-ppa))

WebGL Renderer false

GPU Accelerated Windows 0/1

..................... pls help me to overcome this problem.................

Comment 2

[Daniel Veditz [:dveditz]]

Do you have any crash id's?  Without knowing where it's crashing we can't tell if it's in our code or if it's in the system drivers, or whether the crash is a potential security problem or harmless (but annoying). It will be far easier for you to give us that information than it will be for us to round up that exact hardware/driver combination.

Comment 3

[Govardhana]

this is the crash report which i getting when crash happened.............

Add-ons: {b9db16a4-6edc-47ec-a1f4-b86292ed211d}:4.9.7,[e-mail]:2.4.4,[e-mail]:1.1.2,[e-mail]:9.0,[e-mail]:0.9.3,[e-mail]:2.0.2,[e-mail]:9.0,{972ce4c6-7e08-4474-a285-3208198ce6fd}:9.0
BuildID: 20111124194641
CrashTime: 1323310683
EMCheckCompatibility: true
Email: [e-mail]
FramePoisonBase: 00000000f0dea000
FramePoisonSize: 4096
InstallTime: 1322308945
Notes: OpenGL: Tungsten Graphics, Inc -- Mesa DRI Intel(R) Ironlake Mobile x86/MMX/SSE2 -- 1.4 (2.1 Mesa 7.12-devel (git-c87d1a3 natty-oibaf-ppa)) -- texture_from_pixmap
WebGL? libGL.so.1? libGL.so.1+
GL Context? GL Context+
X_GLXRender: GLXBadRenderRequest; 2 requests agoxpcom_runtime_abort(###!!! ABORT: X_GLXRender: GLXBadRenderRequest; 2 requests ago: file /build/buildd/firefox-9.0~b3+build1/build-tree/mozilla/toolkit/xre/nsX11ErrorHandler.cpp, line 199)
ProductName: Firefox
ReleaseChannel: beta
StartupTime: 1323310445
Theme: classic/1.0
Throttleable: 1
URL: https://cvs.khronos.org/svn/repos/registry/trunk/public/webgl/sdk/demos/google/san-angeles/index.html
Vendor: Mozilla
Version: 9.0

This report also contains technical information about the state of the application when it crashed.

Comment 4

[Daniel Veditz [:dveditz]]

It's the "technical information about the state of the application when it crashed" that we need. If you open the page about:crashes you should see links to the submitted information. The ones that start with "bp-" have been submitted, those are the ones we need.

If they don't start with bp- they are "pending" -- Firefox was unable to submit (possibly because it received a "back-off" response from an overloaded server). You can click those, and if they turn into bp- links or take you to a page on our crash-stats server then those could be useful at that point. The number can change, you can't just take a local ID and stick bp- in front of it.

Comment 5

[Al Billings [:abillings - ex-MoCo]]

Resolving this as incomplete based on a lack of information.

If we can get the crash reports mentioned in comment 4 from about:crashes, please reopen it and we will act on the issue.