Bug 202038 - Flaky Test: inspector/canvas/resolveContext-bitmaprenderer.html
Summary: Flaky Test: inspector/canvas/resolveContext-bitmaprenderer.html
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: WebKit Commit Bot
URL:
Keywords:
Depends on:
Blocks: 50856
  Show dependency tree / graph
 
Reported: 2019-09-20 01:27 PDT by WebKit Commit Bot
Modified: 2019-09-25 15:20 PDT (History)
2 users (show)

See Also:

Attachments
Archive of layout-test-results from webkit-cq-01 (3.27 MB, application/zip)
2019-09-20 01:27 PDT, WebKit Commit Bot 		no flags Details
Archive of layout-test-results from webkit-cq-01 (3.27 MB, application/zip)
2019-09-23 15:26 PDT, WebKit Commit Bot 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description WebKit Commit Bot 2019-09-20 01:27:29 PDT 
This is an automatically generated bug from the commit-queue.
inspector/canvas/resolveContext-bitmaprenderer.html has been flaky on the commit-queue.

inspector/canvas/resolveContext-bitmaprenderer.html was authored by drousso@apple.com.
https://trac.webkit.org/browser/trunk/LayoutTests/inspector/canvas/resolveContext-bitmaprenderer.html

The commit-queue just saw inspector/canvas/resolveContext-bitmaprenderer.html flake (DumpRenderTree crashed) while processing attachment 379134 [details] on bug 201713.
Bot: webkit-cq-01  Port: <class 'webkitpy.common.config.ports.MacPort'>  Platform: Mac OS X 10.13.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.
Comment 1 WebKit Commit Bot 2019-09-20 01:27:30 PDT 
Created attachment 379224 [details]
Archive of layout-test-results from webkit-cq-01
Comment 2 Alexey Proskuryakov 2019-09-20 12:10:49 PDT 
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   ???                           	000000000000000000 0 + 0
1   com.apple.WebCore             	0x000000010d6e4a39 WebCore::WebGLProgram::~WebGLProgram() + 473 (InspectorInstrumentation.h:1634)
2   com.apple.WebCore             	0x000000010d6e4bee WebCore::WebGLProgram::~WebGLProgram() + 14 (RefCounted.h:186)
3   com.apple.JavaScriptCore      	0x00000001084e9164 void JSC::MarkedBlock::Handle::specializedSweep<true, (JSC::MarkedBlock::Handle::EmptyMode)1, (JSC::MarkedBlock::Handle::SweepMode)1, (JSC::MarkedBlock::Handle::SweepDestructionMode)1, (JSC::MarkedBlock::Handle::ScribbleMode)0, (JSC::MarkedBlock::Handle::NewlyAllocatedMode)1, (JSC::MarkedBlock::Handle::MarksMode)1, JSC::JSDestructibleObjectDestroyFunc>(JSC::FreeList*, JSC::MarkedBlock::Handle::EmptyMode, JSC::MarkedBlock::Handle::SweepMode, JSC::MarkedBlock::Handle::SweepDestructionMode, JSC::MarkedBlock::Handle::ScribbleMode, JSC::MarkedBlock::Handle::NewlyAllocatedMode, JSC::MarkedBlock::Handle::MarksMode, JSC::JSDestructibleObjectDestroyFunc const&) + 180 (JSDestructibleObjectHeapCellType.cpp:37)
4   com.apple.JavaScriptCore      	0x00000001084e7b30 void JSC::MarkedBlock::Handle::finishSweepKnowingHeapCellType<JSC::JSDestructibleObjectDestroyFunc>(JSC::FreeList*, JSC::JSDestructibleObjectDestroyFunc const&)::'lambda'()::operator()() const + 384
Comment 3 WebKit Commit Bot 2019-09-23 15:26:00 PDT 
The commit-queue just saw inspector/canvas/resolveContext-bitmaprenderer.html flake (DumpRenderTree crashed) while processing attachment 379393 [details] on bug 201675.
Bot: webkit-cq-01  Port: <class 'webkitpy.common.config.ports.MacPort'>  Platform: Mac OS X 10.13.6
Comment 4 WebKit Commit Bot 2019-09-23 15:26:01 PDT 
Created attachment 379399 [details]
Archive of layout-test-results from webkit-cq-01
Comment 5 Alexey Proskuryakov 2019-09-25 15:20:01 PDT 
r250114 was rolled back in r250139, shouldn't this be marked as resolved?