false. Intentional crash in Internals.cpp |
|||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=5427798229647360 Fuzzer: mbarbella_js_mutation_layout Job Type: linux_ubsan_vptr_content_shell_drt Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: false. Intentional crash in Internals.cpp blink::Internals::crash v8::internal::FunctionCallbackArguments::Call Minimized Testcase (0.04 Kb): Download: https://cluster-fuzz.appspot.com/download/AMIfv97SqOcm4jsx1GLs6nYmHKuDOBMavwJUrfDTvYZEgMXC_3LHwU6IkyWeHe039r-6vof-t2qpsPgdPE7MRiO7qudYUk1lLcuo2terYZ2xCXUMxHBzGSAvFK19neyDdCG-Wtptwv1wYCEXMbTiAGE0ahFokz-FDA?testcase_id=5427798229647360 <script> internals.crash(); </script> Issue filed automatically. See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
Oct 20 2016
I think this is an intentional crash, so I'm not sure that there's anything to do here? Am I missing something?
,
Oct 20 2016
Also, @mmohammad - why are you assigning these blink crashes to me (i.e., how did you get my name)? I'm wondering if we should be using some other triaging mechanism ...
,
Oct 20 2016
Yeah, this is definitely an intentional crash. I'll blacklist it in CF.
,
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 mmohammad@chromium.org
, Oct 20 2016Status: Assigned (was: Untriaged)