Hi Andrea,

Thank you for pointing this out. I wasn't aware of that restriction, and
I appreciate the clarification. Codex performed the investigation and
coding while I exercised the applications and checked their behavior.
I understand that our generated code is not eligible for inclusion in
Wine; I am not asking the project to accept it. My immediate goal is
simply to make these applications useful on my Linux desktop.

I would still welcome diagnostic guidance, if this modified setup is
appropriate for discussion here. A fresh test using the same local
clip twice showed Movie Maker's resident memory grow from about 1.9 to
3.1 GiB across two import/playback passes, with New Project between
them. Restarting between projects remains our workaround. This does
not establish a leak, its owner, or whether stock Wine behaves the
same way. Is there a recommended way to identify the retained
allocations? I can provide the exact setup, measurements and logs,
without submitting generated patches or proprietary binaries.

Thank you for Wine and any guidance.

Larry Dighera