Memory locking issue...

[AlwaysHope]

With 16GB of DDR4 in system. The one in "System Specs" of my profile.
Trying to run this with 14+GB of ram for testing purposes, but program reports can't lock memory for testing as it complaines OS or an app is using it.
I only have the OS running with nothing else, it's not even updating OS... etc..
Have to cut it down to 9216MB, & only then can the testing run.

Wondering if this is a bug or not?

 

[W1zzard]

This is an issue with MemTest64, no issue with your computer.

It seems to have to do with how I allocate memory, and how Windows like the memory to be allocated, but I haven't found a definitive work around yet.

 

[AlwaysHope]

This is an issue with MemTest64, no issue with your computer.

It seems to have to do with how I allocate memory, and how Windows like the memory to be allocated, but I haven't found a definitive work around yet.

Thanks, I'm running it again today but with 10240MB this time, it seems happy with that atm.

 

[baryluk]

Hi I have similar issue. I am running via Wine on Linux, and it fails to lock memory. It is probably because Wine doesn't properly emulate some Windows API (i.e. translate it into mlock / mlockall / mmap(MAP_LOCKED)). I want to run it anyway, because I in fact disabled swap so I know that any real filled anonymous pages are in physical RAM, so they do not need to be really locked. (I am running from Live CD with no hard drives, etc). So a checkbox to run anyway without locking would be nice.

Actually please ignore this. I checked ulimit -l and maximal locked memory size for process / user was 16MB. I raised limits / executed from super user, and I can use about 50GB of memory easily with locking. Works good on Wine 3.0.3 (which is pretty old version).