Issue metadata
Sign in to add a comment
|
GPU FYI WIndows debug bots failure |
||||||||||||||||||||||
Issue descriptionFailure on all windows debug bots on GPU FYI waterfall. Example failure build: https://build.chromium.org/p/chromium.gpu.fyi/builders/Win7%20Debug%20%28AMD%29/builds/1981
,
May 19 2017
melandory@ -- I see subresource_filter::SubresourceFilterSafeBrowsingClient in the stack so assigning to you.
,
May 19 2017
,
May 19 2017
Also failing on Linux Debug Intel 530. https://build.chromium.org/p/chromium.gpu.fyi/builders/Linux%20Debug%20%28Intel%20HD%20530%29/builds/1744 Suspected CL in range is https://codereview.chromium.org/2889913002 which is being reverted right now.
,
May 19 2017
Some of the debug bots are already cycling back green: https://build.chromium.org/p/chromium.gpu.fyi/builders/Win7%20Debug%20%28AMD%29
,
May 23 2017
Sorry this slipped through the cracks in my email. It looks like the same underlying problem as issue 723960 (calling vector::back on an empty vector). It should be fixed now. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by kbr@chromium.org
, May 19 2017Labels: -Type-Bug -Pri-3 Pri-1 Type-Bug-Regression