[BUG] Extop faults while rendering the two-processor dashboard #3

Closed
opened 2026-10-18 12:15:31 +02:00 by erikinkinen · 2 comments
Owner

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-positive scenario at
44a5bc5b. It launches extop --samples=2 with two virtual processors. This was
observed 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, Integration
44a5bc5b6c52225d12aa9cff50bd95a8c5c3a533; release build, dev runtime
configuration, 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

  • Reuse one dashboard line buffer while preserving output, clipping, sink error order and the existing stack budget.
  • Complete strict Cargo checks and inspect the compiled renderer/stream call frames.
  • Pass the original two-processor Extop guest scenario.

Related: Extop audit,
phase completion.

## 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-positive` scenario at `44a5bc5b`. It launches `extop --samples=2` with two virtual processors. This was observed 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`, Integration `44a5bc5b6c52225d12aa9cff50bd95a8c5c3a533`; release build, dev runtime configuration, 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](https://git.erikinkinen.fi/erix/integration/actions/runs/2867/jobs/1/attempt/1). 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 - [x] Reuse one dashboard line buffer while preserving output, clipping, sink error order and the existing stack budget. - [x] Complete strict Cargo checks and inspect the compiled renderer/stream call frames. - [x] Pass the original two-processor Extop guest scenario. Related: [Extop audit](https://git.erikinkinen.fi/erix/extop/issues/1), [phase completion](https://git.erikinkinen.fi/erix/integration/issues/65).
Author
Owner

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.

Published [223ba3fa](https://git.erikinkinen.fi/erix/extop/commit/223ba3fafe280e52c517a49cb498ff8537e357fa). 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.
Author
Owner

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.

The original two-processor guest scenario passes in [CI2870](https://git.erikinkinen.fi/erix/integration/actions/runs/2870/jobs/1/attempt/1) on [Integration 6f20e691](https://git.erikinkinen.fi/erix/integration/commit/6f20e691142054bfae65eaf52d0fa5c3788879f8), using [Extop 223ba3fa](https://git.erikinkinen.fi/erix/extop/commit/223ba3fafe280e52c517a49cb498ff8537e357fa). Its CPU, memory, process and exit checks are unchanged; the out-of-session refusal control also passes. [PR 2](https://git.erikinkinen.fi/erix/extop/pulls/2) contains the fix. The remaining Integration catalog is still running.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:33:52 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
erix/extop#3
No description provided.