DanielLeens commented on issue #9863: URL: https://github.com/apache/seatunnel/issues/9863#issuecomment-5125124916
There is now concrete follow-up progress on this issue. A draft fix PR has been opened as #11593, and it is targeting the shared Arrow reader cleanup path that this Doris failure goes through. The current fix direction is to release the Arrow stream reader and related owned resources before closing the allocator, which matches the leak pattern described earlier in this thread. So at this point, this issue is no longer only waiting for more symptoms. It is being tracked through an actual code fix on `dev`. The next practical step is: 1. let #11593 finish review and CI; 2. once a build containing that change is available, verify whether your Doris job no longer fails with the same memory-leak exception; 3. if it still reproduces after that, please update this thread with the new stack trace and exact build information, because that would indicate there is still a Doris-specific path beyond the shared Arrow reader cleanup. Also, since this project tracks issues in English, please try to provide any follow-up details in English if possible. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
