Closed Bug 703567 Opened 14 years ago Closed 14 years ago

WebGL crash on ASUS tablet with Flight of the Navigator demo

Categories

(Core :: Graphics: CanvasWebGL, defect)

x86_64
Linux
defect
Not set
critical

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: kairo, Unassigned)

Details

(Keywords: crash)

Crash Data

This bug was filed from the Socorro interface and is report bp-784f6d13-de28-4c22-a5da-6dc3d2111118 . ============================================================= Top stack frames: 0 libc.so abort 1 libc.so dlfree 2 libc.so free 3 libstdc++.so _ZdaPvRKSt9nothrow_t 4 libxul.so TOutputESSL::writeVariablePrecision _new.h:135 5 libxul.so TOutputGLSLBase::writeVariableType gfx/angle/src/compiler/OutputGLSLBase.cpp:123 6 libxul.so TOutputGLSLBase::visitAggregate gfx/angle/src/compiler/OutputGLSLBase.cpp:540 7 libxul.so TIntermAggregate::traverse gfx/angle/src/compiler/IntermTraverse.cpp:135 8 libxul.so TOutputGLSLBase::visitAggregate gfx/angle/src/compiler/OutputGLSLBase.cpp:454 9 libxul.so TIntermAggregate::traverse gfx/angle/src/compiler/IntermTraverse.cpp:135 10 libxul.so TranslatorESSL::translate gfx/angle/src/compiler/TranslatorESSL.cpp:27 11 libxul.so TCompiler::compile gfx/angle/src/compiler/Compiler.cpp:182 12 libxul.so ShCompile gfx/angle/src/compiler/ShaderLang.cpp:186 13 libxul.so mozilla::WebGLContext::CompileShader content/canvas/src/WebGLContextGL.cpp:4488 14 libxul.so nsIDOMWebGLRenderingContext_CompileShader obj-firefox/js/xpconnect/src/dom_quickstubs.cpp:23809 15 libxul.so js::InvokeKernel js/src/jscntxtinlines.h:297 This reproducibly happens with the current (XUL UI) Nightly when I start up http://videos.mozilla.org/serv/mozhacks/flight-of-the-navigator/ on my ASUS Transformer tablet (Android 3.2.1), and pretty early when loading. As no driver is involved in the stack, it looks to me very much as it's a bug in the ANGLE code we have in our tree.
Summary: crash abort → WebGL crash on ASUS tablet with Flight of the Navigator demo
I tried reproducing this on my Fennec native (birch) debug build and I get exactly the same hang symptoms as in bug 703569.
(In reply to Christian Holler (:decoder) from comment #1) > I tried reproducing this on my Fennec native (birch) debug build and I get > exactly the same hang symptoms as in bug 703569. As native uses the same process for rendering, while my build uses a content process, that could very well be the same thing, then. I'll try the test in the other bug on my tablet tomorrow.
(In reply to Christian Holler (:decoder) from comment #1) > I tried reproducing this on my Fennec native (birch) debug build and I get > exactly the same hang symptoms as in bug 703569. For me (on a XUL UI build), it's different. With the one here, I get a clear content crash that is reported and the content process can be restarted from the crash reporter dialog. With those conformance tests, the content process becomes unresponsive, no reporter dialog comes up, and the only thing that helps is to get the Nightly process killed somehow.
No longer hangs or crashes on Fennec Native. I suspect an ANGLE update fixed the issue.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
Verified on my tablet and the XUL version of Fennec, so we should also be good for this (not that the actual demo does work too well, but there's no crash any more).
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.