For testing purposes, I’m running a ReactOS-based web server on https://reactos.aaron.cc/ (I posted about an HTTPS issue recently, which I was able to solve).
In general, the server runs quite well, however, after some time (maybe a week), it seems to run out of memory and freezes.
Code: Select all
Aug 21 04:57:23 vultr qemu-system-i386[58926]: (ntoskrnl/mm/ARM3/pfnlist.c:113) Running low on pages: 26 remaining
Aug 21 04:57:23 vultr qemu-system-i386[58926]: (ntoskrnl/mm/ARM3/pfnlist.c:113) Running low on pages: 25 remaining
Aug 21 04:57:23 vultr qemu-system-i386[58926]: (ntoskrnl/mm/ARM3/pfnlist.c:113) Running low on pages: 24 remaining
Aug 21 04:57:23 vultr qemu-system-i386[58926]: (ntoskrnl/mm/ARM3/pfnlist.c:113) Running low on pages: 23 remaining
Aug 21 04:57:23 vultr qemu-system-i386[58926]: (ntoskrnl/mm/ARM3/pfnlist.c:113) Running low on pages: 22 remaining
Aug 21 04:57:23 vultr qemu-system-i386[58926]:
Aug 21 04:57:23 vultr qemu-system-i386[58926]: *** Assertion failed: MmAvailablePages >= 32
Aug 21 04:57:23 vultr qemu-system-i386[58926]: *** Source File: /srv/buildbot/worker_data/Build_GCCLin_x86/build/ntoskrnl/mm/ARM3/pagfault.c, line 656
Aug 21 04:57:23 vultr qemu-system-i386[58926]:
Aug 21 04:57:23 vultr qemu-system-i386[58926]: Break repeatedly, break Once, Ignore, terminate Process or terminate Thread (boipt)?
I’m running the following dev build: 20220808-0.4.15-dev-4916-gd519b11.GNU_8.4.0
Is it worth creating a bug report for this?
Aaron