Null-dereference READ in blink::EventTarget::IsTopLevelNode |
||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5830893382664192 Fuzzer: ifratric-browserfuzzer-v3 Job Type: linux_ubsan_chrome Platform Id: linux Crash Type: Null-dereference READ Crash Address: 0x000000000000 Crash State: blink::EventTarget::IsTopLevelNode blink::WheelEvent::preventDefault v8::internal::FunctionCallbackArguments::Call Sanitizer: undefined (UBSAN) Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=578690:578695 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5830893382664192 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Jul 27
Automatically applying components based on crash stacktrace and information from OWNERS files. If this is incorrect, please apply the Test-Predator-Wrong-Components label.
,
Jul 27
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/667f001d9507c6ba636c93b1a831f333f5f475d8 (Add use counter for document level wheel event listeners.). If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.
,
Jul 28
This crash occurs very frequently on windows platform and is likely preventing the fuzzer ifratric-browserfuzzer-v3 from making much progress. Fixing this will allow more bugs to be found. Marking this bug as a blocker for next Beta release. If this is incorrect, please add ClusterFuzz-Wrong label and remove the ReleaseBlock-Beta label.
,
Jul 28
,
Jul 30
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fac41025a9b9a43d31c66d6f4eccf92649ec51ba commit fac41025a9b9a43d31c66d6f4eccf92649ec51ba Author: Sahel Sharify <sahel@chromium.org> Date: Mon Jul 30 22:00:10 2018 Check currentTarget != null befire checking if it is top level or not. Bug: 868584 Change-Id: Ifa831ebeb3c7b2b86dc9cb5d56d122085eabfec1 Reviewed-on: https://chromium-review.googlesource.com/1155148 Commit-Queue: Sahel Sharify <sahel@chromium.org> Reviewed-by: Dave Tapuska <dtapuska@chromium.org> Cr-Commit-Position: refs/heads/master@{#579185} [modify] https://crrev.com/fac41025a9b9a43d31c66d6f4eccf92649ec51ba/third_party/blink/renderer/core/events/wheel_event.cc
,
Jul 31
ClusterFuzz has detected this issue as fixed in range 579184:579185. Detailed report: https://clusterfuzz.com/testcase?key=5830893382664192 Fuzzer: ifratric-browserfuzzer-v3 Job Type: linux_ubsan_chrome Platform Id: linux Crash Type: Null-dereference READ Crash Address: 0x000000000000 Crash State: blink::EventTarget::IsTopLevelNode blink::WheelEvent::preventDefault v8::internal::FunctionCallbackArguments::Call Sanitizer: undefined (UBSAN) Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=578690:578695 Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=579184:579185 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5830893382664192 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.
,
Jul 31
ClusterFuzz testcase 5830893382664192 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by ClusterFuzz
, Jul 27