mirror of
https://github.com/tangerineturtle1/NX2navi.git
synced 2026-11-15 21:29:58 -04:00
The review of c05e6528 found two texts that said more than the code or the logs do. - runtime/perf_census.h stated as fact that the replaying thread's write-watch queries wait for the walk's address-space lock. The verifier's caveat stands: in the session the charge is based on, the presenting thread's 600-frame memory report (vk_memory.c vk_mem_census) ran at the same frames as the walks, and the log cannot tell which of the two held the 63 replay hitches up. The comment now says they sat beside such a walk, that the charge assumes the walk held them up, and that a play-test with mem_census = 0 checks it. - nx2navi.ini.example's mem_census paragraph said the "mem: process" line comes every 600 frames. Since c05e6528, vk_memory.c heap_log leaves its own walk out at a frame where perf.c census_check walked (every 3600th frame, and a commit census on growth that falls on a 600th), and the commit census lines stand in for it; the paragraph says so. Comment and settings text only. perf.c compiles with the dev flags; census_charge_check passes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2.2 KiB
2.2 KiB