SaelixCode 0db6c946e7 fix(logs): cap DOM rendering to 300 rows to prevent OOM crash ...

Playwright investigation revealed the Logs view (GlobalObservabilityView)
rendered 1,859+ log entries as real DOM nodes (9,616 total DOM nodes) with
no virtualization. Combined with a 5-second polling cycle replacing all
React elements each time and smooth-scroll animations stacking on every
update, the renderer process grew rapidly on a host running at 97% RAM
usage, crashing the browser tab with Out of Memory within minutes.

Fixes:
- Cap rendered DOM rows to MAX_DISPLAY_ROWS (300) via .slice(-300) so the
  browser only ever holds ~1,500 log-related DOM nodes regardless of how
  many entries are in state
- Add a truncation notice when log count exceeds the display cap
- Reduce SSE-mode in-memory log cap from 10,000 to MAX_LOG_ENTRIES (2,000)
- Switch auto-scroll from behavior:'smooth' to behavior:'instant' to stop
  stacking layout animations on every 5-second poll
- Reduce /api/logs/global response limit from 2,000 to 500 lines since the
  client renders at most 300 rows, making the extra payload wasteful

2026-03-20 11:59:24 -04:00

..

public

feat: add frontend index.html and Vite logo; enhance system stats API with network metrics

2026-02-26 14:43:45 -05:00

src

fix(logs): cap DOM rendering to 300 rows to prevent OOM crash

2026-03-20 11:59:24 -04:00

cookies.txt

feat: add alert management functionality in NotificationSettingsModal and implement stacks API endpoint

2026-02-27 09:52:54 -05:00

package-lock.json

refactor: pivot from ssh proxy to distributed api model

2026-03-19 12:20:32 -04:00

package.json

refactor: pivot from ssh proxy to distributed api model

2026-03-19 12:20:32 -04:00

tsconfig.json

Initial commit: Sencho V1 complete with Auth and Dockerization

2026-02-20 18:39:32 -05:00