> We don't have to have STR, but it would be nice if we could verify that (In reply to Joe Drew (:JOEDREW!) from comment #20) In the meantime QA will try to see if one of our vendors has the machine/graphics card Joe notes in Comment 9, or procure one ourselves to do some testing on.
> blocking these devices will actually help us. > with our beta population if we see enough of the crashes there. What's the user experience when their video card is blocked? Is it just a perf hit when doing graphics accelerated tasks?įrom the query in, it does appear that we have enough crashes in bug 728533 alone to notice the difference after blocking. Retesting using Mozilla/5.0 (Windows NT 6.1 WOW64 rv:12.0) Gecko/20100101 Firefox, here is the output from the XML file:Īticf圆4 aticf圆4 aticf圆4 aticfx32 aticfx32 aticfx32 atiumd64 atidx圆4 atidx圆4 atiumdag atidxx32 atidxx32 atiumdva atiumd6a atitmm64 *%2C+nsIFrame*%2C+nsRect+const%26%2C+nsDisplayListSet+const%26%2C+unsigned+int%29&reason=&build_id=&process_type=any&hang_type=any&do_query=1 I'd be up for moving forward with a test like this in FF11 beta 5 (go-to-build tomorrow 2/28) if you think this is our best chance at quashing all of the bugs blocked here and the user effect isn't too severe. Retesting, using Mozilla/5.0 (Windows NT 6.1 WOW64 rv:12.0) Gecko/20100101 Firefox/12.0 with a fresh profile:ī_override.buildID ANGLE (AMD Radeon HD 6310 Graphics) - OpenGL ES 2.0 (ANGLE 1.0.0.963) I tested the staged block in Comment 70 on the Radeon Machine and it doesn't seem to be picking up the block at all in blocklist.xml.Ģ.
Ping by pasting the snippet in the error console Set params according to and include for the block.ģ. Retesting with the staged block I see this now is working:īlocked for your graphics card because of unresolved driver issues.
0 kommentar(er)
