Null-dereference in blink::Internals::textAffinity |
||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4664022149627904 Fuzzer: inferno_layout_test_unmodified Job Type: windows_syzyasan_content_shell Platform Id: windows Crash Type: Null-dereference Crash Address: 0x00000017 Crash State: blink::Internals::textAffinity blink::V8Internals::textAffinityAttributeGetterCallback v8::internal::FunctionCallbackArguments::Call Memory Tool: SYZYASAN Regressed: https://clusterfuzz.com/revisions?job=windows_syzyasan_content_shell&range=510722:510724 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4664022149627904 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Oct 31 2017
,
Oct 31 2017
Automatically applying components based on crash stacktrace and information from OWNERS files. If this is incorrect, please apply the Test-Predator-Wrong-Components label.
,
Oct 31 2017
,
Oct 31 2017
,
Nov 1 2017
Predator and CL could not provide any possible suspects. Using the code search for the file, “Internals.cpp” assigning to concern owner. Suspecting Commit# https://chromium.googlesource.com/chromium/src/+/f01e385c3f752c2bfd1163db74ecbf88e5390d25 fserb@ -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes. Thank You.
,
Nov 2 2017
ClusterFuzz has detected this issue as fixed in range 513227:513290. Detailed report: https://clusterfuzz.com/testcase?key=4664022149627904 Fuzzer: inferno_layout_test_unmodified Job Type: windows_syzyasan_content_shell Platform Id: windows Crash Type: Null-dereference Crash Address: 0x00000017 Crash State: blink::Internals::textAffinity blink::V8Internals::textAffinityAttributeGetterCallback v8::internal::FunctionCallbackArguments::Call Memory Tool: SYZYASAN Regressed: https://clusterfuzz.com/revisions?job=windows_syzyasan_content_shell&range=510722:510724 Fixed: https://clusterfuzz.com/revisions?job=windows_syzyasan_content_shell&range=513227:513290 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4664022149627904 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.
,
Nov 2 2017
ClusterFuzz testcase 4664022149627904 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Nov 7 2017
|
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by kkaluri@chromium.org
, Oct 24 2017