CHECK failure: message->data_num_bytes() < GetConfiguration().max_message_num_bytes in node_cha |
||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5120482063155200 Fuzzer: inferno_twister Job Type: mac_asan_content_shell 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_content_shell&range=501804:501852 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5120482063155200 Additional requirements: Requires HTTP Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Sep 25 2017
This crash is intentional.
,
Sep 26 2017
,
Sep 27 2017
,
Oct 1 2017
,
Oct 2 2017
ClusterFuzz testcase 5120482063155200 is still reproducing on tip-of-tree build (trunk). If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase. Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by kkaluri@chromium.org
, Sep 25 2017Components: Internals>Mojo
Labels: M-63 Test-Predator-Wrong
Owner: roc...@chromium.org
Status: Assigned (was: Untriaged)