New issue
Advanced search Search tips

Issue 853621 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Jun 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug



Sign in to add a comment

Breakpoint in blink::FirstLetterPseudoElement::DidRecalcStyle

Project Member Reported by ClusterFuzz, Jun 18 2018

Issue description

Detailed report: https://clusterfuzz.com/testcase?key=5081751857397760

Fuzzer: bj_broddelwerk
Job Type: windows_asan_chrome_no_sandbox
Platform Id: windows

Crash Type: Breakpoint
Crash Address: 0xffffbb84d0a20800
Crash State:
  blink::FirstLetterPseudoElement::DidRecalcStyle
  blink::Element::RecalcStyle
  blink::Element::UpdatePseudoElement
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=567613:567614

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5081751857397760

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for more information.
 
Project Member

Comment 1 by ClusterFuzz, Jun 18 2018

Components: Blink>DOM
Labels: Test-Predator-Auto-Components
Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.
Project Member

Comment 2 by ClusterFuzz, Jun 18 2018

Labels: Test-Predator-Auto-Owner
Owner: futhark@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/9b2c8f90be4d44a0fa8799d3253820e975841e52 ([Squad] Remove special code path for reattach recalc.).

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.
Project Member

Comment 3 by bugdroid1@chromium.org, Jun 18 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/de5c18194ce923fa5eeec84881ffcf96554d98f7

commit de5c18194ce923fa5eeec84881ffcf96554d98f7
Author: Rune Lillesveen <futhark@chromium.org>
Date: Mon Jun 18 14:59:25 2018

Do not override kReattach for ::first-letter.

We incorrectly did an override with kForce for ::first-letter recalc
when we were already recalculating style for re-attachment (kReattach).
This caused crashes in FirstLetterPseudoElement::DidRecalcStyle.

Bug:  853621 ,  853476 ,  853471 ,  853470 ,  853433 ,  853411 
Change-Id: Id34e6bdbaaeb3b4933a3e963b68f0bffcda0e40e
Reviewed-on: https://chromium-review.googlesource.com/1104176
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Anders Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568006}
[add] https://crrev.com/de5c18194ce923fa5eeec84881ffcf96554d98f7/third_party/WebKit/LayoutTests/external/wpt/css/css-pseudo/first-letter-block-to-inline-ref.html
[add] https://crrev.com/de5c18194ce923fa5eeec84881ffcf96554d98f7/third_party/WebKit/LayoutTests/external/wpt/css/css-pseudo/first-letter-block-to-inline.html
[modify] https://crrev.com/de5c18194ce923fa5eeec84881ffcf96554d98f7/third_party/blink/renderer/core/dom/element.cc

Status: Fixed (was: Assigned)
Project Member

Comment 5 by ClusterFuzz, Jun 19 2018

ClusterFuzz has detected this issue as fixed in range 568005:568006.

Detailed report: https://clusterfuzz.com/testcase?key=5081751857397760

Fuzzer: bj_broddelwerk
Job Type: windows_asan_chrome_no_sandbox
Platform Id: windows

Crash Type: Breakpoint
Crash Address: 0xffffbb84d0a20800
Crash State:
  blink::FirstLetterPseudoElement::DidRecalcStyle
  blink::Element::RecalcStyle
  blink::Element::UpdatePseudoElement
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=567613:567614
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=568005:568006

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5081751857397760

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.
Project Member

Comment 6 by ClusterFuzz, Jun 19 2018

Labels: ClusterFuzz-Verified
Status: Verified (was: Fixed)
ClusterFuzz testcase 5081751857397760 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