Memory leak check

[myungjoo]

Fix potential memory leak in _ml_info_set_value when g_strdup(key) fails due to out-of-memory.

The original design correctly handled memory deallocation during normal ml_service_destroy paths. However, if g_strdup(key) failed within _ml_info_set_value (e.g., due to OOM), the value and info_value allocated prior to the g_strdup call would not be freed, leading to a leak. This change ensures these resources are properly released in such an error scenario.

---

 

[cursor]

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}