Bug 44345 - WebGL cars demo crash in llvm::Type::getForwardedTypeInternal()
Summary: WebGL cars demo crash in llvm::Type::getForwardedTypeInternal()
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Mesa core (show other bugs)
Version: git
Hardware: Other All
: medium normal
Assignee: mesa-dev
QA Contact:
URL: http://www.chromeexperiments.com/deta...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-31 05:25 UTC by Pavel Ondračka
Modified: 2012-07-19 16:29 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
terminal output and backtrace (41.14 KB, text/plain)
2011-12-31 05:25 UTC, Pavel Ondračka
Details

Description Pavel Ondračka 2011-12-31 05:25:58 UTC
Created attachment 55004 [details]
terminal output and backtrace

WebGL Cars from chrome Experiments crash when using i915g or r300g with RADEON_NO_TCL=1 set.

Program received signal SIGSEGV, Segmentation fault.
0x02c1e108 in llvm::Type::getForwardedTypeInternal() const () from /home/Marie/mesa/lib/gallium//i915_dri.so

Full terminal output and backtrace attached.

Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02)
OpenGL renderer string: Gallium 0.4 on i915 (chipset: 945G)
OpenGL version string: 2.0 Mesa 7.12-devel (git-99fbf7c)
Firefox: 9.0.1
LLVM version: 2.9-4.fc16
Comment 1 Pavel Ondračka 2012-01-23 08:39:16 UTC
This regression can be also reproduced with llvmpipe, however you need to set webgl.force-enabled to true in about:config (Firefox doesn't enable webgl for llvmpipe by default).
Comment 2 Pavel Ondračka 2012-01-23 08:40:04 UTC
Ah, sorry wrong bug.
Comment 3 Jose Fonseca 2012-07-19 16:29:38 UTC
This should have be fixed, as part of.

commit 3469715a8a171512cf9b528702e70393f01c6041
Author: José Fonseca <jfonseca@vmware.com>
Date:   Fri Jul 13 18:09:30 2012 +0100

    gallivm,draw,llvmpipe: Support wider native registers.

as we not longer recreate LLVMContexts.

Please reopen if it's still there.


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.