Make the memory report's system line name the write-combined views, the recording copies and the handles.

The system line took the driver's device-local figure out of the process's commit, but the driver's write-combined views of that memory came to 0.2-1.1 GiB more, and that part went to "other": in the 2026-11-13 session other system memory grew 1,283 MiB in play while the process's own commit grew 307. With a walk of the address space (mem_census) less than a minute old, the gap at that walk is now a term of its own. The NVN recording copies, malloc'd, count among the C runtime heap's known parts with those unused for 5 minutes, and the line ends with the process's handle count, which rose at every area load in that session and never fell.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
chrg6
2026-11-13 12:48:00 -05:00
parent cacb1318fc
commit 67cef75920
4 changed files with 39 additions and 8 deletions

View File

@@ -2248,6 +2248,15 @@ void plat_process_memory(uint64_t *resident, uint64_t *private_bytes) {
fclose(f);
}
uint32_t plat_handle_count(void) {
DIR *d = opendir("/proc/self/fd");
if (!d) return 0;
uint32_t n = 0;
for (struct dirent *e; (e = readdir(d));) n += e->d_name[0] != '.';
closedir(d);
return n ? n - 1 : 0; // less the descriptor of this walk
}
// glibc's mallinfo2 (2.33 and later) sums every arena: arena is what the arenas took with brk and mmap, hblkhd the
// blocks mmapped one by one, uordblks what the arenas handed out. Other C libraries leave the figures unknown.
void plat_heap_info(PlatHeapInfo *h) {