92287 2012-07-25 13:20:11 -0700 [Chromium] context-creation-and-destruction layout tests are slow 2013-04-08 15:03:35 -0700 1 1 1 Unclassified WebKit Canvas 528+ (Nightly build) Unspecified Unspecified RESOLVED WONTFIX P2 Normal --- 76225 1 atwilson kbr bajones cmarrin dglazkov dino gman kbr schenney tdanderson zmo oldest_to_newest 678388 0 atwilson 2012-07-25 13:20:11 -0700 These tests are slow (landed as part of r123556, I guess): fast/canvas/webgl/context-creation-and-destruction.html = PASS platform/chromium/virtual/gpu/fast/canvas/webgl/context-creation-and-destruction.html = PASS http://test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=fast%2Fcanvas%2Fwebgl%2Fcontext-creation-and-destruction.html I've marked them SLOW in TestExpectations 701012 1 kbr 2012-08-21 12:43:52 -0700 Committed r126180: <http://trac.webkit.org/changeset/126180> 800494 2 tdanderson 2013-01-04 12:12:44 -0800 These are starting to fail sometimes, so I have updated TestExpectations accordingly: http://trac.webkit.org/changeset/138827 802326 3 dglazkov 2013-01-08 10:12:00 -0800 This test is now consistently timing out, even marked as "Slow". 802348 4 kbr 2013-01-08 10:30:05 -0800 I'm going to remove this test. It was added for Bug 76255 but the "fix" for that bug (which is still evolving in Bug 104733) wasn't actually tested by this test. 802356 5 gman 2013-01-08 10:37:53 -0800 The point of this test is for a hypothetical site similar to docs.google.com. Imagine a sight that makes graphs from spreadsheets. For certain effects they create a WebGL context, render a graph, make an image, then kill the WebGL context (ie, let it go) Such a site shouldn't stop working after a certain number of context create-use-destroy cycles. 802378 6 kbr 2013-01-08 10:53:34 -0800 The test can be added again once there is code in WebKit supporting it. Right now WebKit imposes no limit on the number of WebGL contexts that can be allocated nor on the amount of memory that can be allocated by all WebGL contexts. Having either of those two limits in place would let the test in the Khronos repository run successfully and then we could re-introduce a stripped down version as a layout test. It is a little distressing though that not even 8 iterations of the test can run within the timeout.