Ken, this is still causing startup crashes on MSan build and blocking fuzzing, can you please take a look.

On it.

Should be good, offending CL reverted.

ClusterFuzz has detected this issue as fixed in range 490017:490023.

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

Fuzzer: bj_broddelwerk
Job Type: linux_msan_content_shell_drt
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  mojo::edk::ChannelPosix::WriteNoLock
  mojo::edk::ChannelPosix::Write
  mojo::edk::NodeChannel::SendChannelMessage
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=489756:489860
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=490017:490023

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


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 6540645014700032 is verified as fixed, so closing issue as verified.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.

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