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/+/e71aa45ab3098edca75725a658d3624f5ed47108 (INPUT/TEXTAREA elements: Fix incorrect selectionStart/selectionEnd values after blur.).

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.

My CL is unrelated to this stack.
No suspicious changes in the regression range.

Predator and CL could not provide any possible suspects.

Using Code Search for the file, "Node.cpp" and observed there was some recent changes for the below file.

Suspect CL: https://chromium.googlesource.com/chromium/src/+/199f150cd5633d45678e35c6b90d75e5baa0f021%5E%21/third_party/WebKit/Source/core/dom/Node.cpp

tzik@ -- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks!

No. It's unrelated.

Unable to find actual suspect through code search and also from the provided CL, hence adding appropriate label fir further triage.

Thanks!

Assigning to the Style team TL

I was not able to reproduce this locally.

ClusterFuzz has detected this issue as fixed in range 546993:546996.

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

Fuzzer: marty_html_twiddler
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: Direct-leak
Crash Address: 
Crash State:
  blink::Node::SetNonAttachedStyle
  blink::Element::RecalcStyleForReattach
  blink::ContainerNode::RecalcDescendantStylesForReattach
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=471280:471296
Fixed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=546993:546996

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

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 6012839123484672 is verified as fixed, so closing issue as verified.

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