Skip to content

Conversation

@myungjoo
Copy link
Member

Fix memory leak in ml_service_new/ml_service_destroy loop by ensuring server->id is properly initialized and reset.

The server->id was not consistently initialized or reset, causing ml_agent_pipeline_destroy() to be skipped or called with an incorrect ID, leading to server-side pipeline resource leaks during repeated ml_service_new() and ml_service_destroy() calls.


Open in Cursor Open in Web

@cursor
Copy link

cursor bot commented Dec 10, 2025

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
Learn more about Cursor Agents

@myungjoo myungjoo closed this Dec 10, 2025
@myungjoo myungjoo deleted the cursor/fix-ml-service-memory-leak-308c branch December 15, 2025 04:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants