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
..
COMPATIBILITY.md	feat(ci): add release workflow + update readme	2026-09-29 00:15:21 +03:00
INPUT_MAPPING.md	refactor(docs): separated user and dev in docs + compatibility file	2026-09-28 22:58:17 +03:00
USAGE.md	fix(libkernel): state the size of a direct memory backing Windows cannot create	2026-10-05 17:52:04 +02:00