Not much actionable here, but I strongly doubt there's an actual leak anywhere. 32-bit games running out of address space isn't exactly a new or uncommon issue, and literally any change in the past 8 months could be enough to push it over the edge.
Ya didn't expect there to be much to do. Just weird that this is one of the most solid running games over the years and all of a sudden it has these errors fairly frequently and only with dxvk after 2.7.1. If you want to close it, or I can try to test next release, or current git-head when I get the time.
Did you enable the exe's LAA flag? (if that's possible to do on Linux) That might help. (as 32-bit games can only access up to 2 GB of memory; LAA doubles that to 4 GB)
this is of course assuming the game doesn't have LAA enabled by default
It doesn't have it by default, though unless OP is playing 8K or has modded textures going out of memory shouldn't be happening.
Just vanilla, only 'mod' was the d9 dll I renamed/moved for black textures. Do not have LAA currently, have a old LAA exe in my lla dir so I had that at one point but would have been ages ago.
It doesn't have it by default, though unless OP is playing 8K or has modded textures going out of memory shouldn't be happening.
The idea would be to download a LAA patcher. (such as one linked here: https://www.techpowerup.com/forums/threads/large-address-aware.112556/) I would assume there are some for Linux. (or, since OP's using WINE, the Environment Variable "WINE_LARGE_ADDRESS_AWARE=1" (without quotes) should work; don't quote me on it though as I don't use Linux)
I like to use this below native tool to enable LAA (needs to be compiled from source though).
System information
Mass Effect 1 (original).
Tried to remove the 'black texture' patch I have for AMD cpus as well as upgrading various things above, no difference for anything until downgrading dxvk.
The git commit in question should be from Feb 6, so I assume the issue is from https://github.com/doitsujin/dxvk/commit/00b59900d3d3aace5e59b46d23e47132223015e1 back to 2.7.1 at https://github.com/doitsujin/dxvk/commit/c3dd74be6baec53786d4e064a572185b70347a17. This was to test the wine fix for Fallout3 fullscreen https://github.com/doitsujin/dxvk/pull/5387 (note: this doesn't fully fix that fo3 issue as after a while fo3 starts minimizing and not restoring and needs killed. Also, there was no minimizing or alt+tab'ing involved with this me1 memleak/crash.)
Apitrace file(s)
Not really possible? Last I've done these they slow things down and take huge amount of data. Playing for 30minutes doesn't really seem viable? I had a autosave before a crash, which I hard saved at thinking it'd immediately crash within a minute again - but it doesn't (crashed after 30min right after autosave, then hard save almost immediately, then hard save let me just keep playing for 30min).
Log files
Wine output just says something about virtual mem allocation (10.1 is flooded with it, 11.3 is just a line or 2, so I assume that's a wine thing).
I got a silent crash then started trying to run from terminal to see if there was anything, played another 30min or so and got a stack trace once then another time this pop-up which is from MassEffect itself afaict.
winecrash-dxvk-stack.txt
Comments
Not sure how to reproduce to get anything useful for debugging. If there's any ideas besides trying to bisect and play for 30min at a time lmk.