User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.3a1pre) Gecko/20100102 Minefield/3.7a1pre Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.3a1pre) Gecko/20100102 Minefield/3.7a1pre webgl turned on in about:config Reproducible: Always Steps to Reproduce: 1.turn on webgl 2.Visit provided link 3. Actual Results: Same as above Expected Results: displayed a webgl picture of some kind
Please provide a stacktrace and update your video driver. https://developer.mozilla.org/En/How_to_get_a_stacktrace_for_a_bug_report
I have two PC boxes with different OS, one is XP pro while the other is win7 ultimate. Software: Firefox nightly Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.3a6pre) Gecko/20100619 Minefield/3.7a6pre Webgl is enabled for all sites. Every time I visit the demo here: http://cubicvr.org/CubicVR.js/BloomTest1.html My Win7 always tell me "Driver crash and restarted" and the Firefox is hanging forever without crash, so there is no crash report. XP box works fine. Hardware: XP Win7 Intel Prescott 3G AMD Phenom II X2 555 880G 915P Embedded ATI4250 Nvidia GTX 7900GTX OGL 3.0 support OGL 2.0 support, 3.0 partial. If I set to use direct2d renderer, it also crashes.
Oops, typing mistake: Hardware: XP Win7 Intel Prescott 3G AMD Phenom II X2 555 915P 880G Nvidia GTX 7900GTX Embedded ATI4250 OGL 2.0 support, 3.0 partial OGL 3.0 support DDR2 667/553 4G DDR3 1600
Dupe of this, i think? https://bugzilla.mozilla.org/show_bug.cgi?id=553089
Reporter, are you still seeing this issue with Firefox 4 beta 10 or later in safe mode or a fresh profile? If not, please close. These links can help you in your testing. http://support.mozilla.com/kb/Safe+Mode http://support.mozilla.com/kb/Managing+profiles
This bug has had the CLOSEME tag for several weeks and the date in the tag is far gone. If the reporter can still see this issue, Please retest with Firefox 3.6.x or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). Then please remove the closeme tag in the whiteboard, mark the bug against the proper version and comment on the bug.