http://bugs.winehq.org/show_bug.cgi?id=59857 --- Comment #10 from Giang Nguyen <nen24t@gmail.com> --- (In reply to Stian Low from comment #8)
Created attachment 81159 [details] Screenshots Serum2 RSS memory grows indefinitely for Reaper (773_x64) and Bitwig (6.0.6-x64) for wine-11.11-13289668fd1
That lines up with what I found when I profiled this earlier, and your gl-vs-vulkan result is the key point: it leaks under both renderers but not under no3d, so it's not the GPU driver — it's CPU-side in the shared wined3d path, as you suspect. The growth lands in Wine's ntdll process heap and tracks the wined3d/d2d1 allocation churn from the redraws; the GPU-driver mappings themselves stay flat. I've attached the profiling data above I collected earlier — measurements only, in case it saves time. It matches your "shared wined3d code" direction and shows where those allocations end up: the growth is entirely in anonymous mappings (the NVIDIA GL-driver mappings and glibc [heap] stay flat, so not the GPU driver, consistent with your gl-vs-vulkan / no3d result), and it is the ntdll *process heap* that keeps growing — all other heaps stay under 4 MiB. The attachment has the per-heap and smaps breakdowns and where the commits originate, with method. Happy to re-run with different instrumentation if that's useful. -- 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.