https://bugs.winehq.org/show_bug.cgi?id=55143
--- Comment #13 from Rafał Mużyło galtgendo@o2.pl --- If it actually *is* a memory consumption / VMS problem, it would *at minimum* take the devs figuring out why so much memory is being consumed.
Btw., for a 32bit windows program, you don't have 16GB, only 4 - and that includes all the backend libs.
As for seeing if it's pure OOM or the VMS variant, you can see VMS values in /proc/<pid>/status (top also shows that value in its default setup).