Closed Bug 1283780 Opened 8 years ago Closed 5 years ago

Intermittent webgl-color-test.html?16bpp&readback&premult&_____ == http://10.0.2.2:8854/tests/dom/canvas/test/reftest/wrapper.html?colors-no-alpha.png | application crashed [@ jemalloc_crash]

Categories

(Core :: Graphics: CanvasWebGL, defect, P5)

defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: cbook, Unassigned)

References

()

Details

(Keywords: crash, intermittent-failure, Whiteboard: gfx-noted)

Bulk assigning P3 to all open intermittent bugs without a priority set in Firefox components per bug 1298978.
Priority: -- → P3
Component: General → Canvas: WebGL
Seems to have stopped.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
Stopped like "I looked at all the failures in the hidden Android webgl tests, and this particular one no longer happens," or like "oh, I forgot these bugs were all Android and Android webgl tests have been hidden since early September"?
Tough to tell: current mozilla-release looks like I remember them looking, swathes of jemalloc crashes and the like, mozilla-beta introduced an odd permafailure in gl5 while retaining close to the same volume of jemalloc crashes, aurora and trunk still have the gl5 failure, added a lot of assertions and crashes in mozilla::MediaShutdownManager::BlockShutdown, and might have dropped the percentage of jemalloc crashes, not sure.
Well I'm not seeing anything at https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1283780&endday=2016-11-28&startday=2016-09-28&tree=all . Please let me know how else I should quantify. When we un-hide android webgl, we'll probably see this reopened.
Jeff, did you actually look at Treeherder before claiming this is gone? OrangeFactor is only going to tell you information on failures that were actually classified by someone, which isn't going to be happening if the test suite is hidden by default unless someone on the Graphics team has been monitoring those results and classifying failures as they occur. Still looks pretty terrible AFAICT, though as philor already pointed out, it's pretty hard to make any reasonable conclusions about the current state of this specific failure when Android M(gl) is permafailing for a multitude of other reasons at the moment. https://treeherder.mozilla.org/#/jobs?repo=mozilla-central&filter-searchStr=android%20webgl&exclusion_profile=false
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Ok.
Priority: P3 → P5
Whiteboard: gfx-noted
Status: REOPENED → RESOLVED
Closed: 8 years ago5 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.