Some devices are failing CoreStartup with M64ERR_NO_MEMORY

[fzurita]

@bsmiles32 It seems like recent change is breaking many Android devices. Specifically this commit:

143cfa7#diff-fa9734f1550e974c80b15a8a6fed3ad7

A lot of devices are failing with M64ERR_NO_MEMORY on CoreStartup.

Is there any way to fallback to the old behavior if we are unable to allocate that much RAM?

So far this error has been limited to Samsung devices.

[bsmiles32]

I think the problem here is that either for their device overcommitting is disabled or that their malloc implementation doesn't use an anonymous mmap internally. I think replacing the malloc/free with mmap/munmap (VirtualAlloc/VirtualFree for Win32) will fix this. Will do a PR when I get back home.

[fzurita]

I replaced malloc and free with

 g_mem_base = mmap(NULL,0x20000000,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANONYMOUS,-1,0);
munmap(g_mem_base,0x20000000);

It seems to run, but I haven't gotten results from devices with the issue yet. I will report back when I do.

[fzurita]

The above didn't work for them, it instead crashed when accessing the memory. I'm having them try your pull request next.

[bsmiles32]

@fzurita Can you try this : #474

[fzurita]

Ok, I'll let you know when I can.