Null-dereference READ in blink::StyleAdjuster::AdjustComputedStyle |
|||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4853575373815808 Fuzzer: inferno_twister Job Type: linux_msan_content_shell_drt Platform Id: linux Crash Type: Null-dereference READ Crash Address: 0x000000000020 Crash State: blink::StyleAdjuster::AdjustComputedStyle blink::StyleResolver::PseudoStyleForElementInternal blink::StyleResolver::PseudoStyleForElement Sanitizer: memory (MSAN) Regressed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=532379:532380 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4853575373815808 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Jan 29 2018
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/d1fe575dbeb077ce496b11c05bd92aed93289831 ([css-align] Add use counter for the 'legacy' alignment). 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.
,
Jan 29 2018
,
Jan 30 2018
ClusterFuzz has detected this issue as fixed in range 532735:532736. Detailed report: https://clusterfuzz.com/testcase?key=4853575373815808 Fuzzer: inferno_twister Job Type: linux_msan_content_shell_drt Platform Id: linux Crash Type: Null-dereference READ Crash Address: 0x000000000020 Crash State: blink::StyleAdjuster::AdjustComputedStyle blink::StyleResolver::PseudoStyleForElementInternal blink::StyleResolver::PseudoStyleForElement Sanitizer: memory (MSAN) Regressed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=532379:532380 Fixed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=532735:532736 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4853575373815808 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. |
|||
►
Sign in to add a comment |
|||
Comment 1 by ClusterFuzz
, Jan 29 2018