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

Feels like the meaning stacktrace are the following:

#12 0x8ace872 in IPC::MessageT<LayoutTestHostMsg_SimulateWebNotificationClick_Meta, std::__1::tuple<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, base::Optional<int>, base::Optional<std::__1::basic_string<unsigned short, base::string16_internals::string16_char_traits, std::__1::allocator<unsigned short> > > >, void>::MessageT(IPC::Routing, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, base::Optional<int> const&, base::Optional<std::__1::basic_string<unsigned short, base::string16_internals::string16_char_traits, std::__1::allocator<unsigned short> > > const&) ipc/ipc_message_templates_impl.h:29
#13 0x8ae37ab in MessageT<true, false> ipc/ipc_message_templates.h:130:9
#14 0x8ae37ab in SimulateWebNotificationClick content/shell/renderer/layout_test/blink_test_runner.cc:314

Added component label

bpastene@, could you take a look at this one?
Please feel free to reassign. 

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

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

Not sure why this was assigned to me. I have no context or relevance here.

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/3689f3e57b85ca683cc6b61841715fbd0c6af559 (Add crashGpuProcess() to gpu_benchmarking_extension.).

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.

If my CL is at fault then this is because Clusterfuzz is running with --enable-gpu-benchmarking and testing privileged APIs, which it shouldn't be.

ClusterFuzz has detected this issue as fixed in range 582653:582655.

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

Fuzzer: inferno_twister
Job Type: linux_msan_content_shell_drt
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  void base::Pickle::WriteBytesStatic<4ul>
  IPC::TupleParamTraitsHelper<std::__1::tuple<std::__1::basic_string<char, std::__
  IPC::MessageT<LayoutTestHostMsg_SimulateWebNotificationClick_Meta, std::__1::tup
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=581064:581078
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=582653:582655

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

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.

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