Bug: assimp:assimp_roundtrip_fuzzer: Direct-leak in Assimp::XFileParser::ParseFile

Sanitizer: address (ASAN)

Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_assimp&range=202607020607:202607030651

Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=6232318252220416

Issue filed automatically.

See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally.
When you fix this bug, please
* mention the fix revision(s).
* state whether the bug was a short-lived regression or an old bug in any stable releases.
* add any other useful information.
This information can help downstream consumers.

If you need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. Comments on individual Monorail issues are not monitored.

This bug is subject to a 90 day disclosure deadline. If 90 days elapse
without an upstream patch, then the bug report will automatically
become visible to the public.

Start with the OSS-Fuzz reproducing instructions and testcase 6232318252220416, running the assimp_roundtrip_fuzzer under ASAN. Trace the direct leak to Assimp::XFileParser::ParseFile and inspect the surrounding parser ownership and cleanup paths. Done means the testcase no longer reports the leak and the fix revision and regression status are documented.

Written by the indexing model from the issue text.