http://bugs.winehq.org/show_bug.cgi?id=59857 --- Comment #7 from Stian Low <wineryyyyy@gmail.com> --- (In reply to Giang Nguyen from comment #6)
So yabridge can be ruled out as the cause: it reproduces both via yabridge (REAPER) and in a yabridge-free pure-Wine stack (FL Studio).
Thanks for clarifying. Wine indeed seems likely bugged. If similar to other bugs for games with similar reported memory leaks then Serum may be easier for reproducing it.
NVIDIA AD107GL [RTX 2000 Ada Generation] [10de:28b0] This is a hybrid-graphics machine and also has an Intel Arrow Lake-U iGPU [8086:7d67], but the GL renderer string confirms Wine renders through the NVIDIA card.
It seems neither of your GPUs are explicitly supported by wine which may mean they fallback to defaults with low memory ~1.5 GB. Adding support for a missing GPU recently seemed to improve reporters performance so it may be a factor regarding memory leaks: https://bugs.winehq.org/show_bug.cgi?id=59186 I'll take a closer look whether falling back to low GPU defaults may be causing memory leaks somewhere. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.