Null-dereference READ in content::RenderWidget::OnDidOverscroll |
||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5420196063084544 Fuzzer: ochang_domfuzzer Job Type: linux_asan_content_shell_drt Platform Id: linux Crash Type: Null-dereference READ Crash Address: 0x000000000008 Crash State: content::RenderWidget::OnDidOverscroll content::RenderWidgetInputHandler::DidOverscrollFromBlink blink::ChromeClientImpl::DidOverscroll Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_asan_content_shell_drt&range=519320:519321 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5420196063084544 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Nov 28 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.
,
Nov 28 2017
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/dc8d14d9a16b28d12b8380d0a5490fe4a747a65a (Enable mojo input messages on all platforms other than Android webview.). If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.
,
Nov 28 2017
ClusterFuzz has detected this issue as fixed in range 519420:519421. Detailed report: https://clusterfuzz.com/testcase?key=5420196063084544 Fuzzer: ochang_domfuzzer Job Type: linux_asan_content_shell_drt Platform Id: linux Crash Type: Null-dereference READ Crash Address: 0x000000000008 Crash State: content::RenderWidget::OnDidOverscroll content::RenderWidgetInputHandler::DidOverscrollFromBlink blink::ChromeClientImpl::DidOverscroll Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_asan_content_shell_drt&range=519320:519321 Fixed: https://clusterfuzz.com/revisions?job=linux_asan_content_shell_drt&range=519420:519421 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5420196063084544 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 28 2017
ClusterFuzz testcase 5420196063084544 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
, Nov 28 2017