Null-dereference READ in blink::PaintLayer::ContainingLayer |
|||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6286351489302528 Fuzzer: bj_broddelwerk Job Type: linux_asan_chrome_mp Platform Id: linux Crash Type: Null-dereference READ Crash Address: 0x000000000010 Crash State: blink::PaintLayer::ContainingLayer blink::AccumulateOffsetTowardsAncestor blink::PaintLayer::VisualOffsetFromAncestor Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_mp&range=508951:508952 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6286351489302528 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Oct 15 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 15 2017
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/945b31d85a3f01f5bb59e9c52f244aa704f28e27 (Compute a fragmented offset for control clips of input boxes.). If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.
,
Oct 16 2017
,
Oct 16 2017
,
Oct 17 2017
ClusterFuzz has detected this issue as fixed in range 509194:509202. Detailed report: https://clusterfuzz.com/testcase?key=6286351489302528 Fuzzer: bj_broddelwerk Job Type: linux_asan_chrome_mp Platform Id: linux Crash Type: Null-dereference READ Crash Address: 0x000000000010 Crash State: blink::PaintLayer::ContainingLayer blink::AccumulateOffsetTowardsAncestor blink::PaintLayer::VisualOffsetFromAncestor Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_mp&range=508951:508952 Fixed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_mp&range=509194:509202 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6286351489302528 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 7 2017
,
Nov 7 2017
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by ClusterFuzz
, Oct 15 2017