Wine crashes - continued

[kingsombra]

I might have found some interesting information about the wine crashes that I have been experiencing. I think it might be the following:

cat /proc/sys/vm/max_map_count
65530

From quite a long time of reading different things on the net, everything says that this value is far too low if you want to run any kind of games at all under wine. Unfortunately this is the default value in OM.

Some suggest just go hole hog and max it out to 2147483642.

Could I get some help on the correct way to increase this permanently?

Everything I have read says to add it to:
/etc/sysctl.conf

Unfortunately, this does not seem to exist on OM so I am not sure how to do this correctly.

[sez11a (Rich Sezov)]

Try /etc/sysctl.d/99-sysctl.conf.

[vannax (Mike)]

I use WINE to run a little image manipulation program.
My sysctl.d folder is empty.

[zeroability]

@kingsombra

From quite a long time of reading different things on the net, everything says that this value is far too low if you want to run any kind of games at all under wine. Unfortunately this is the default value in OM.

Some suggest just go hole hog and max it out to 2147483642.

Since Valve’s Proton is also based on Wine, you would expect this to affect that as well. It doesn’t seem to. Which either means there is a bug in Wine, which will need to be reported, or some configuration overlap from copying full backups of a home drive into a fresh home drive. We can’t really help in either case, and not knowing what you are running makes that even more difficult.

[LinNoob]

@zeroability

Since Valve’s Proton is also based on Wine, you would expect this to affect that as well. It doesn’t seem to. Which either means there is a bug in Wine, which will need to be reported, or some configuration overlap from copying full backups of a home drive into a fresh home drive. We can’t really help in either case, and not knowing what you are running makes that even more difficult.

I had to change this file to get DayZ to run through steam on OM. It was step 5 on my install documentation.

Installing DayZ on OpenMandriva Linux from Steam

This write up is shamelessly taken from Playing DayZ on Arch Linux | Space Bums and Some documentation on vm.max_map_count · Issue #141 · lutris/docs · GitHub with a tweak or two for installing on OpenMandriva and updates to the Steam interface. While I love OM there really is not much documentation for installing games which makes it a little more difficult for super noobs like me to use it the way I want to. Step 1. Install Steam from OMWelcome. Dont install it other way as you may introduce …

[zeroability]

@LinNoob

I had to change this file to get DayZ to run through steam on OM. It was step 5 on my install documentation.

This is probably a better resource:
https://www.protondb.com/app/221100

[LinNoob]

@zeroability

This is probably a better resource:

https://www.protondb.com/app/221100

That page is where I first found out about changing the map count, DayZ refused to run without doing it.

[zeroability]

@kingsombra

cat /proc/sys/vm/max_map_count

The reports over the past few days don’t mention it. It does mention a memory leak, though. Which is how you get to the setting in the first place:

https://www.kernel.org/doc/html/latest/admin-guide/sysctl/vm.html

max_map_count:

"This file contains the maximum number of memory map areas a process may have. Memory map areas are used as a side-effect of calling malloc, directly by mmap, mprotect, and madvise, and also when loading shared libraries.

While most applications need less than a thousand maps, certain programs, particularly malloc debuggers, may consume lots of them, e.g., up to one or two maps per allocation.

The default value is 65530."

[zeroability]

Here is some more specific info:

DayZ (221100)

I guess, what I’m getting at is we have no way of knowing what someone is going to use it for and tuning the kernel will need testing before being applied to a default config.

[LinNoob]

I wouldn’t recommend even trying to tune or applying the fix to the kernel on account of this DayZ bug because Dayz is the epitome of janky code. Just trying to show the OP what I did to to maybe fix his issue, if it even is his issue.

My write up shows how to do it with or without making permanent changes to his system.

[zeroability]

Understood. Just putting all the variables out there for consideration.