CHECK failure: message->data_num_bytes() < GetConfiguration().max_message_num_bytes in node_cha |
||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5678064221814784 Fuzzer: miaubiz_svg_fuzzer Job Type: mac_asan_chrome Platform Id: mac Crash Type: CHECK failure Crash Address: Crash State: message->data_num_bytes() < GetConfiguration().max_message_num_bytes in node_cha mojo::edk::NodeChannel::WriteChannelMessage mojo::edk::NodeChannel::SendChannelMessage Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=508393:508470 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5678064221814784 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Nov 10 2017
Predator and CL could not provide any possible suspects. Using the code search for the file, “node_channel.cc” assigning to concern owner. Suspecting Commit# https://chromium.googlesource.com/chromium/src/+/55090272269b587b30cc3eb277184644c4b16088 erikchen@ -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes. Thank You.
,
Nov 10 2017
,
Nov 10 2017
|
||||
►
Sign in to add a comment |
||||
Comment 1 by ClusterFuzz
, Nov 10 2017