Automatically applying components based on crash stacktrace and information from OWNERS files.

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

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/00710b48b6d06931a868dc6982b0daafd8875560 (Simplify scroll to fragment code).

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.

I've tried this locally with my patch reverted and it still crashes - we hit this DCHECK:

[117461:117483:0427/184021.351482:FATAL:container_node.cc(315)] Check failed: !target_node->parentNode(). 

This is an issue in DOM so I'm unassigning myself. I've kicked off a regression range task in the bug, hopefully that'll find a better suspect.

Here's a simpler repro file. It's still quite contrived but I cannot get a simpler one.

Deleted: repro.svg 2.2 KB

repro.svg 2.2 KB Download

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

commit 93ca91184f00306ac91660014266d6b664f80cfb
Author: Fergal Daly <fergal@chromium.org>
Date: Mon Jun 25 09:09:54 2018

DOM: Handle cross-document node moves correctly.

The current NeedsRecheck checks whether the node's document version has increased
by more than 1 but it does not notice when the node has moved to a new document.

Since we cannot capture the original version of the final document for
comparison, we have to assume that when the document changes, a recheck is
needed.

Bug:  837377 
Change-Id: If83c4eaeb6b737768cc45c2f3a2241b03d3d2e75
Reviewed-on: https://chromium-review.googlesource.com/1109667
Reviewed-by: Kent Tamura <tkent@chromium.org>
Commit-Queue: Fergal Daly <fergal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569988}
[add] https://crrev.com/93ca91184f00306ac91660014266d6b664f80cfb/third_party/WebKit/LayoutTests/dom/node/appendChild-document-crash.html
[modify] https://crrev.com/93ca91184f00306ac91660014266d6b664f80cfb/third_party/blink/renderer/core/dom/container_node.cc

ClusterFuzz has detected this issue as fixed in range 569987:569988.

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

Fuzzer: inferno_twister_c
Job Type: linux_tsan_chrome_mp
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000010
Crash State:
  blink::Element::InsertedInto
  blink::SVGElement::InsertedInto
  blink::ContainerNode::NotifyNodeInsertedInternal
  
Sanitizer: thread (TSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=523922:523942
Fixed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=569987:569988

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

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.

ClusterFuzz testcase 6103925741322240 is verified as fixed, so closing issue as verified.

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