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 On Saturday, October 10, 2026 at 01:42:13 PM PDT, Andrea Faulds via Wine-Devel <wine-devel@list.winehq.org> wrote: Hi Larry, On Sat, 10 Oct 2026, at 17:50, Larry Dighera via Wine-Devel wrote:
Hello Wine developers.
With OpenAI Codex's help, I am bringing Forté Agent, Paint Shop Pro and Windows Movie Maker to Debian 12.
This modified setup uses Wine 11.0,
I am myself a very new Wine developer, so don't take this message as coming from a place of any authority, and I apologise if you are already aware of this, but you may want to know that Wine's clean-room policy prohibits use of LLMs (including for example via Codex) to generate code: https://gitlab.winehq.org/wine/wine/-/wikis/Clean-Room-Guidelines Of course, that would only be relevant if you want to contribute the code back to Wine. As for your actual question, I can't help with that, myself. Best regards, Andrea Faulds