https://bugs.winehq.org/show_bug.cgi?id=53737
--- Comment #9 from Paul Gofman pgofman@codeweavers.com --- (In reply to Paul Gofman from comment #8)
From the log:
I am not sure if we can do anything sensible about it now, I don't have immediate feasible ideas how we can deal with variable kernel stack size (and I think reverting it to the older size will break more than fix). Long term with 32 on 64 that shouldn't be an issue as kernel stack is going to be 64 bit.
Here I mean the change introduced by the blame commit specifically. Outside of that (especially if reverting the commit of top on master yields the same VRAM exhaustion), it looks a bit weird that a ddraw game hits that, it may happen that there are issues in ddraw or elsewhere which lead to excessive VRAM usage which can be fixed.