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

lukasza@, could you take a look at this issue since you changed content/shell/test_runner/test_runner_for_specific_view.cc recently?

Thanks! Please feel free to re-assign.

Hmmm.... I can't repro with:

clusterfuzz reproduce 4718189436207104 -j 1500 -l 25 -i 20
# also no repro:
# with --disable-xvfb
# with --current (@ r483912 / 03322108cedb2b380926f58c507157828c6db4f2)
#       although in this case I had to tweak args.gn to work around a compile error

I don't think this should be marked as ReleaseBlock-Stable, as the problem is only present in test code (i.e. in content/shell/test_runner).

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

 Issue 733460  has been merged into this issue.

+security sheriffs - can you please review the release blocker status (see #c7 and #c8 above).

+tanin@ - thank you for helping get a more reliable repro in issue 739498.  I'll try to take a closer look next week.

If we are sure that this is test only code, please feel free to remove the label again, though I don't know to tell ClusterFuzz not to revert that.

Removing ReleaseBlock-Stable (see #c7 and #c12) again and adding ReleaseBlock-NA (see #c8 - I think this is supposed to prevent reapllying ReleaseBlock-Stable).

 Issue 740389  has been merged into this issue.

FWIW, I tried to repro using the steps from https://crbug.com/739498#c5 and I couldn't get a local repro... :-/

ClusterFuzz has detected this issue as fixed in range 488838:488842.

Detailed report: https://clusterfuzz.com/testcase?key=4718189436207104

Fuzzer: inferno_layout_test_unmodified
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=420372:420473
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=488838:488842

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4718189436207104


See https://github.com/google/clusterfuzz-tools for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

ClusterFuzz testcase 4718189436207104 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 5100461110853632 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.

 Issue 766974  has been merged into this issue.

Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

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