You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by "github-actions[bot] (via GitHub)" <gi...@apache.org> on 2026/03/30 03:19:35 UTC

Re: [I] [Bug] [Module Name] Bug title TaskExecuteThreadPool memory leak [dolphinscheduler]

github-actions[bot] commented on issue #18101:
URL: https://github.com/apache/dolphinscheduler/issues/18101#issuecomment-4151887269

   ### Search before asking
   
   - [x] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
   
   
   ### What happened
   
   3.2.1version TaskExecuteThreadPool.taskExecuteThreadMap memory leak
   
   ### What you expected to happen
   
   Does 3.2.1version really cause memory leaks and how to solve them?
   
   ### How to reproduce
   
   Does 3.2.1version really cause memory leaks and how to solve them?
   
   ### Anything else
   
   _No response_
   
   ### Version
   
   dev
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)


-- 
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: commits-unsubscribe@dolphinscheduler.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org