This is an automatically generated bug from the commit-queue. webgl/2.0.0/conformance/more/functions/drawArrays.html has been flaky on the commit-queue. webgl/2.0.0/conformance/more/functions/drawArrays.html was authored by justin_fan@apple.com. https://trac.webkit.org/browser/trunk/LayoutTests/webgl/2.0.0/conformance/more/functions/drawArrays.html The commit-queue just saw webgl/2.0.0/conformance/more/functions/drawArrays.html flake (DumpRenderTree crashed) while processing attachment 355832 [details] on bug 192060. Bot: webkit-cq-03 Port: <class 'webkitpy.common.config.ports.MacPort'> Platform: Mac OS X 10.12.6 The bots will update this with information from each new failure. If you believe this bug to be fixed or invalid, feel free to close. The bots will re-open if the flake re-occurs. If you would like to track this test fix with another bug, please close this bug as a duplicate. The bots will follow the duplicate chain when making future comments.
Created attachment 355834 [details] Archive of layout-test-results from webkit-cq-03
Thread 46 Crashed:: DFG Worklist Worker Thread 0 com.apple.JavaScriptCore 0x000000010587ef15 JSC::speculationFromValue(JSC::JSValue) + 213 (SpeculatedType.cpp:477) 1 com.apple.JavaScriptCore 0x0000000105852c16 JSC::CodeBlock::valueProfilePredictionForBytecodeOffset(JSC::ConcurrentJSLocker const&, int) + 38 (SpeculatedType.h:473) 2 com.apple.JavaScriptCore 0x000000010595851a JSC::DFG::ByteCodeParser::getPredictionWithoutOSRExit(unsigned int) + 90 (DFGByteCodeParser.cpp:837) 3 com.apple.JavaScriptCore 0x0000000105948c0e void JSC::DFG::ByteCodeParser::parseGetById<JSC::OpGetById>(JSC::Instruction const*) + 126 (DFGByteCodeParser.cpp:889) 4 com.apple.JavaScriptCore 0x0000000105937fd4 JSC::DFG::ByteCodeParser::parseBlock(unsigned int) + 5588 (Instruction.h:45) 5 com.apple.JavaScriptCore 0x000000010594c6ea JSC::DFG::ByteCodeParser::parseCodeBlock() + 810 (DFGByteCodeParser.cpp:7037) 6 com.apple.JavaScriptCore 0x000000010594ca83 JSC::DFG::ByteCodeParser::parse() + 83 (DFGByteCodeParser.cpp:6852)
*** This bug has been marked as a duplicate of bug 192050 ***