Use-of-uninitialized-value in test_runner::TestRunnerForSpecificView::Reset |
||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5855667588694016 Fuzzer: mbarbella_js_mutation_layout Job Type: linux_msan_content_shell_drt Platform Id: linux Crash Type: Use-of-uninitialized-value Crash Address: Crash State: test_runner::TestRunnerForSpecificView::Reset test_runner::WebViewTestProxyBase::Reset test_runner::TestInterfaces::ResetAll Sanitizer: memory (MSAN) Recommended Security Severity: Medium Regressed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=545879:545880 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5855667588694016 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Apr 6 2018
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/279708b3c8ed5b6d9b4ed452072458cb0f9047d0 ([LayoutTests] Replace multiple dump responses with one callback/struct.). If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.
,
Apr 6 2018
Add component labels based on https://chromium.googlesource.com/chromium/src/+/279708b3c8ed5b6d9b4ed452072458cb0f9047d0
,
Apr 6 2018
Comment 3: Thanks-- looks like r545880 was for issue 667551 (No support for OOPIFs when doing image diffs in layout tests).
,
Apr 7 2018
,
Apr 7 2018
This is a serious security regression. If you are not able to fix this quickly, please revert the change that introduced it. If this doesn't affect a release branch, or has not been properly classified for severity, please update the Security_Impact or Security_Severity labels, and remove the ReleaseBlock label. To disable this altogether, apply ReleaseBlock-NA. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 7 2018
,
Apr 9 2018
vmpstr@: Can you take a look? The ClusterFuzz report should have pretty good info on where the problem is.
,
Apr 9 2018
This may very well be a duplicate of issue 671787. I should write up one day why fixing this is difficult and depends on some upfront work like https://crrev.com/c/677864
,
Apr 10 2018
,
Apr 10 2018
Re #9, it does seem like a similar issue. FWIW, I have tried reproducing this and couldn't do it. Mostly because I'm still trying to figure out how to run msan with the new linux distro
,
Apr 12 2018
removing rbs, since this is a layout test issue
,
Apr 12 2018
This is a serious security regression. If you are not able to fix this quickly, please revert the change that introduced it. If this doesn't affect a release branch, or has not been properly classified for severity, please update the Security_Impact or Security_Severity labels, and remove the ReleaseBlock label. To disable this altogether, apply ReleaseBlock-NA. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 12 2018
,
Apr 18 2018
,
May 17 2018
ClusterFuzz testcase 5855667588694016 appears to be flaky, updating reproducibility label.
,
May 18 2018
Is this actually a security bug? It looks like the crash is in test code. If it doesn't affect production code, we can remove the security labels.
,
May 18 2018
RE: #c17 - agreed that this is not really a security bug / the problem is in the test code, not in production code.
,
May 23 2018
ClusterFuzz testcase 5855667588694016 is flaky and no longer crashes, so closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Aug 30
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 ClusterFuzz
, Apr 6 2018