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

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

Predator and CL could not provide any possible suspects.
Using the code search for the file, “cxfa_fm2jscontext.cpp” assigning to concern owner from GIT blame.
Suspecting Commit#
https://pdfium.googlesource.com/pdfium.git/+/275e260a6cd4a8e506ba974feb85ebcd926c1739

@rharrison -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.
Thank You.

Sending over to Dan, since he has been mucking around in the JS code recently, so probably has more context then I.

https://pdfium-review.googlesource.com/c/pdfium/+/25350

ClusterFuzz has detected this issue as fixed in range 535061:535070.

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

Fuzzer: libFuzzer_pdfium_xfa_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: ASSERT
Crash Address: 
Crash State:
  pNode
  CXFA_FM2JSContext::ResolveObjects
  CXFA_FM2JSContext::dot_accessor
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=459173:459235
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=535061:535070

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md 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 4638340845666304 is verified as fixed, so closing issue as verified.

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