ClusterFuzz testcase 5159014924288000 is verified as fixed, so closing issue as verified.
If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
ClusterFuzz testcase 6183129105825792 is still reproducing on tip-of-tree build (trunk).
Please re-test your fix against this testcase and if the fix was incorrect or incomplete, please re-open the bug. Otherwise, ignore this notification and add ClusterFuzz-Wrong label.
Please revisit this, since Clusterfuzz claims it still can repro in comment 20. Is that due to the mega-revert in comment 21? Just the order doesn't seem right, but maybe bugdroid was slow with comment 21?
Thanks for the heads up. I think it was just the mega revert (.. which has been relanded as per comment#23). I can't reproduce this locally with ToT (46488f71bb9b5efed2eb9433ac226c3798477d85) today.
Comment 1 by ClusterFuzz
, Jan 10 2018Owner: machenb...@chromium.org
Status: Assigned (was: Untriaged)