https://bugs.winehq.org/show_bug.cgi?id=33858
--- Comment #20 from Paul Gofman gofmanp@gmail.com --- (In reply to Zebediah Figura from comment #19)
I'm not sure I see how it's useful, given what I said above—ways to relieve address space pressure, if they even exist, may be specific to each application affected by exhaustion.
I don't see how the ways to relieve address space pressure are specific to applications, at least the ones gathered here now. The common problem is that Wine needs more virtual address space than Windows, mostly due to native libraries often eating more address space (with pulseaudio and opengl somewhere on top). Maybe some Wine components could use optimization in that regards too.
It is not a single localized issue in Wine, yes, but what specifics do you see with regards to applications gathered here? And if is anyone going to do something in Wine or some libraries to attempt to relief memory pressure a bit, isn't it easier that the information is linked to the single place, so it is easier to test with different applications?
A bug titled something like "multiple applications exhaust address space" can't really be closed, not even as WONTFIX.
Probably a lot of the multiple individual bugs for this cannot be ever closed the same way, as whatever can be done will reduce the probability of the specific app crash, but will likely not eliminate it completely. If there are convincing enough reasons to think that the issue is about the same, why having distinct records?