Stack-overflow in blink::LayoutObject::FindNextLayer |
||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6363703294033920 Fuzzer: inferno_layout_test_unmodified Job Type: linux_asan_content_shell_drt Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffc171ddfe0 Crash State: blink::LayoutObject::FindNextLayer Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_asan_content_shell_drt&range=544750:544758 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6363703294033920 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
May 31 2018
Automatically applying components based on crash stacktrace and information from OWNERS files. If this is incorrect, please apply the Test-Predator-Wrong-Components label.
,
May 31 2018
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/2a94373409feaf9794c2489ba9563fe67a8eabbd (Make <foreignObject> a stacking context.). 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.
,
Jun 16 2018
ClusterFuzz has detected this issue as fixed in range 567613:567614. Detailed report: https://clusterfuzz.com/testcase?key=6363703294033920 Fuzzer: inferno_layout_test_unmodified Job Type: linux_asan_content_shell_drt Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffc171ddfe0 Crash State: blink::LayoutObject::FindNextLayer Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_asan_content_shell_drt&range=544750:544758 Fixed: https://clusterfuzz.com/revisions?job=linux_asan_content_shell_drt&range=567613:567614 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6363703294033920 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.
,
Jun 16 2018
ClusterFuzz testcase 6363703294033920 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
, May 31 2018