summaryrefslogtreecommitdiff
path: root/src/vmon.c
diff options
context:
space:
mode:
authorVito Caputo <vcaputo@pengaru.com>2025-01-01 11:49:28 -0800
committerVito Caputo <vcaputo@pengaru.com>2025-01-01 19:32:12 -0800
commit707152eeb5d259e4fab41f7c6ed1afea4380968a (patch)
treef42764037ccf53cab360bbf61c844c1690e38bad /src/vmon.c
parent3a7106b731aa58f25dc95b86c706a79c7e8d6ae5 (diff)
libvmon: ignore orphaned followed children still having parents
Now that vmon is a real thing with PID1 monitoring, there's this detail of orphans getting inherited which libvmon has so far largely been able to ignore because vwm doesn't care about such things, always monitoring subtrees attached to X windows. This fixes the vmon asserts when monitoring the PID1 hierarchy where vcr_shift_below_row_up_one() would abort @: >·······assert(*(vcr->hierarchy_end_ptr) >= row); It was being triggered when orphans were found by the PID1 children following while they were still children of their exited-from-kernel's-perspective-but-not-yet-libvmon's-perspective parent process. There's more work to be done to improve this situation, but it's likely going to be quite invasive. For now this is a simple solution that should prevent the asserts. We just might not see a process being orphaned for a sample while it gets ignored for still having its vestigial parent around as is_stale=1.
Diffstat (limited to 'src/vmon.c')
0 files changed, 0 insertions, 0 deletions
© All Rights Reserved