New issue
Advanced search Search tips

Issue 883607 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Oct 12
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

CHECK failure: !is_immutable_ || !scroll_. Value cleared while immutable. Old state: in object_

Project Member Reported by ClusterFuzz, Sep 13

Issue description

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

Fuzzer: bj_broddelwerk
Job Type: linux_debug_chrome
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  !is_immutable_ || !scroll_. Value cleared while immutable. Old state: in object_
  blink::ObjectPaintProperties::ClearScroll
  blink::FragmentPaintPropertyTreeBuilder::UpdateScrollAndScrollTranslation
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=584167:584169

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Sep 13

Components: Blink>Paint
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, Sep 13

Labels: Test-Predator-Auto-Owner
Owner: chaopeng@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/6b253b354bdfe09dbe88e40561e60d2df3a42160 ([blink-gen-property-trees] Always add scroll node for layout view).

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.
Cc: bokan@chromium.org pdr@chromium.org
Not able to repro locally with the clusterfuzz tools.

pdr@ bokan@ do you know anything may related?
Interesting, I'm also unable to repro on a local albeit non-asan and ToT build. I've kicked off a task to recheck the status. Otherwise we should probably reach out to the clusterfuzz team since issues should always be reproducible locally using their tool.
Project Member

Comment 5 by ClusterFuzz, Sep 14

Labels: -Reproducible Unreproducible
ClusterFuzz testcase 5632206859665408 appears to be flaky, updating reproducibility label.
I landed a fix for  issue 875287 . It may also fix this issue.
Project Member

Comment 7 by ClusterFuzz, Oct 12

Status: WontFix (was: Assigned)
ClusterFuzz testcase 5632206859665408 is flaky and no longer crashes, so closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.

Sign in to add a comment