[BUG] Extop faults while rendering the two-processor dashboard #3
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/extop#3
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Extop faults while rendering the initial shell's two-processor dashboard. The
monitor never reaches its memory/process rows or completes the bounded sample run.
Reproduction
Run Integration's
appliance-disk-image-initial-exsh-extop-positivescenario at44a5bc5b. It launchesextop --samples=2with two virtual processors. This wasobserved in original CI2867; no unchanged VM rerun was used.
Expected and actual behavior
Render two complete CPU, memory and process samples, then exit successfully.
Instead, only the heading and CPU0/CPU1 baseline rows appear before the child
page-faults and is killed. The guest's 45-second progress watchdog later expires.
Environment and identity
Extop
357c6476ae72f13cb94e0f52a8cbdd6df28ed0e8, Integration44a5bc5b6c52225d12aa9cff50bd95a8c5c3a533; release build, dev runtimeconfiguration, x86-64 QEMU with two processors. The monitor receives session
inspection and terminal streams, with no process-control capability.
Evidence and prior checks
Original CI2867 job.
The complete terminal log records the page fault and partial dashboard. The
renderer creates a 32,696-byte array inside each specialized line function,
while the executable reserves a 64KiB stack. Nested line allocations are the
suspected cause; compiled frame analysis and guest acceptance remain open.
Tracking
Related: Extop audit,
phase completion.
Published 223ba3fa. The dashboard now reuses one line buffer and retains the existing output boundaries and 64KiB stack. All 11 local Cargo checks passed, including default/all-feature tests and freestanding builds, with no warnings.
The compiled standalone dashboard has one 33,112-byte entry frame; line and stream helpers have small frames. This is not a complete guest stack bound. The original two-processor VM scenario remains open.
The original two-processor guest scenario passes in CI2870 on Integration 6f20e691, using Extop 223ba3fa. Its CPU, memory, process and exit checks are unchanged; the out-of-session refusal control also passes. PR 2 contains the fix. The remaining Integration catalog is still running.