false. Intentional crash in Internals.cpp |
|||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=5955343621554176 Fuzzer: inferno_layout_test_unmodified Job Type: mac_asan_content_shell Platform Id: mac Crash Type: CHECK failure Crash Address: Crash State: false. Intentional crash in Internals.cpp blink::Internals::crash v8::internal::FunctionCallbackArguments::Call Regressed: https://cluster-fuzz.appspot.com/revisions?job=mac_asan_content_shell&range=416628:416781 Minimized Testcase (0.04 Kb): Download: https://cluster-fuzz.appspot.com/download/AMIfv97us3FiNZJdYxHiDT9yROHW3JIHgTWzvMO_rfYTMDdg6sagtVktJLbCXNzytONvSwoRNMG2-poWNCRpCuxtRS8ThyVf_h7FMbxTXDpduO7XPrd_VWQwYOgz8W_nhXdWlJ81Jgb9TofIuYusDZGZPPeslUnySg?testcase_id=5955343621554176 <script> internals.crash(); </script> Issue filed automatically. See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
Nov 16 2016
Looks like something is going wrong with demangling on our mac bots, so the "blink::Internals::crash" entry in our blacklist isn't working here. In the short term I've updated this to be based on the check failed line, but I'll still work on a proper fix on the CF side.
,
Nov 22 2016
Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||
►
Sign in to add a comment |
|||
Comment 1 by tapted@chromium.org
, Nov 16 2016Status: Assigned (was: Untriaged)