AnyPS5/core/libs/prx/libkernel/DirectMemory
Celegans12 62c70fb1d5 fix(libkernel): state the size of a direct memory backing Windows cannot create
On Windows each direct memory allocation is backed by a page-file
section that CreateFileMappingW commits in full. When the system commit
limit cannot cover it, the title stopped with "create direct memory
backing: Insufficient system resources exist to complete the requested
service", which did not say how much was requested.

The error now states the requested size in bytes and MiB, and the
runtime layout notes in USAGE.md describe the commit requirement and
the page file. Allocation behaviour is unchanged: committing at
allocation matches the console, where allocated direct memory is
always backed by physical memory.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-05 17:52:04 +02:00
..
DirectMemory.cpp fix(libkernel): state the size of a direct memory backing Windows cannot create 2026-10-05 17:52:04 +02:00
DirectMemory.hpp fix(libkernel): honour MAP_FIXED in sceKernelReserveVirtualRange and sceKernelMemoryPoolReserve 2026-10-01 00:00:22 +02:00
Export.cpp feat(libkernel): implement sceKernelMlock 2026-10-05 00:25:56 +00:00
MemoryPool.cpp fix(kernel): share direct memory mappings and track physical offsets 2026-09-30 09:59:51 +03:00
MemoryPool.hpp style: drop the branch's code comments per CONVENTIONS.md 2026-09-29 21:25:29 +03:00
MemoryPoolExport.cpp fix(libkernel): honour MAP_FIXED in sceKernelReserveVirtualRange and sceKernelMemoryPoolReserve 2026-10-01 00:00:22 +02:00
PosixMemory.cpp feat(kernel): support private anonymous guest memory mappings 2026-09-25 06:06:31 +10:00