https://bugs.winehq.org/show_bug.cgi?id=43685
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com
--- Comment #10 from Zebediah Figura z.figura12@gmail.com --- The problem that is being described in comments 4 and onward is a general problem, which has no single general cause nor a single general solution. It doesn't really make sense to file a bug for it, perhaps not even in the specific case, since that bug can never be closed.
At best one may offer workarounds, such as not using PulseAudio, or manually setting the IMAGE_FILE_LARGE_ADDRESS_AWARE flag where possible.
(In reply to Shmerl from comment #8)
It's really something that should be handled by Wine itself.
If you mean that Wine should always act as if IMAGE_FILE_LARGE_ADDRESS_AWARE is set, no, it's not. There's a reason that flag exists, and it's that some applications are specifically *not* large address aware, and make assumptions about pointers that are only valid if the address space is limited to the lower 2 GB.