Issue metadata
Sign in to add a comment
|
Crash in blink::Frame::host |
||||||||||||||||||||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=4962741418983424 Fuzzer: meacer_chromebot_extensions Job Type: windows_asan_chrome Platform Id: windows Crash Type: UNKNOWN Crash Address: 0x0cb024c4 Crash State: blink::Frame::host blink::PaintLayerCompositor::updateClippingOnCompositorLayers blink::PaintLayerCompositor::updateIfNeeded Recommended Security Severity: Medium Regressed: https://cluster-fuzz.appspot.com/revisions?job=windows_asan_chrome&range=418438:418789 Minimized Testcase (16.27 Kb): https://cluster-fuzz.appspot.com/download/AMIfv941SyUwQ0l4u2HkOtEy1XMWRVPRU-txAWKUk2bBv86ny3ULu9UsJHydlfVRYXegf0ruNhzf1avM2eRrKTqJ_2jC4zCNUjmKtRpN7CGZC1bw9X3aAUSqCJawe775Vc0L7IS4jI49hWpzy7NZQxLa2DP6y6wgOtyG1eXl2eriCODIrGop0Z4?testcase_id=4962741418983424 Issue filed automatically. See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
Sep 16 2016
This issue is a security regression. If you are not able to fix this quickly, please revert the change that introduced it. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 16 2016
,
Sep 16 2016
Hi David, Assigning this clusterfuzz security bug to you, as it seems related to https://bugs.chromium.org/p/chromium/issues/detail?id=647453. Feel free to adjust labels or re-assign as appropriate. Thanks!
,
Sep 16 2016
,
Sep 19 2016
The crash report seems to be having a hard time reproducing the issue, it's now marked as flaky. The stack trace seems strange because the reference to Frame::host didn't appear until after r418789 in r418868 so I suspect the analysis in the report is wrong. I have tried locally reproducing the crash using downloaded binaries for r418789 and r419399. I was able to consistently repro the crash in the former but not in the latter so I believe the issue is fixed. I'll leave this open for a few more days in hopes that the clusterfuzz page will pick up the fix but I believe the actual issue is fixed.
,
Sep 20 2016
This issue is a security regression. If you are not able to fix this quickly, please revert the change that introduced it. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 20 2016
As noted above, this is likely fixed but the Clusterfuzz bug is confused. Marking as WontFix.
,
Dec 28 2016
This bug has been closed for more than 14 weeks. Removing security view restrictions. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by sheriffbot@chromium.org
, Sep 16 2016