ober/jerboa-signal
1
0
Fork 0
Code Issues 2 Pull requests Projects Releases Packages Wiki Activity Actions

Investigate jsignal process reaching approximately 90GB RSS #8

New issue
Open
opened 2026-09-25 17:44:46 -04:00 by ober · 0 comments
ober commented 2026-09-25 17:44:46 -04:00
Owner
Copy link

Problem

The jsignal process was observed consuming almost 90GB of resident set size. That is far beyond expected steady-state memory use and can put the host at risk of OOM pressure or forced process termination.

Impact

  • Extremely high RSS can destabilize the host running jsignal.
  • If this is a leak, long-running deployments may degrade until restart.
  • If this is unbounded buffering or retained message state, memory may scale dangerously with traffic, queue depth, or reconnect behavior.

Initial investigation targets

  • Reproduce under a controlled long-running workload and capture RSS over time.
  • Inspect heap/object retention around message handling, attachments/media, queues, subscriptions, reconnect loops, and logging buffers.
  • Add or document a memory smoke test/regression guard if the cause is found.
  • Consider defensive limits or backpressure for any unbounded in-memory collections.

Evidence available now

Reported observation: jsignal reached approximately 90GB resident set size. More runtime details still need to be gathered: workload, uptime, platform, process arguments, logs, and whether RSS drops after idle or GC.

## Problem The jsignal process was observed consuming almost 90GB of resident set size. That is far beyond expected steady-state memory use and can put the host at risk of OOM pressure or forced process termination. ## Impact - Extremely high RSS can destabilize the host running jsignal. - If this is a leak, long-running deployments may degrade until restart. - If this is unbounded buffering or retained message state, memory may scale dangerously with traffic, queue depth, or reconnect behavior. ## Initial investigation targets - Reproduce under a controlled long-running workload and capture RSS over time. - Inspect heap/object retention around message handling, attachments/media, queues, subscriptions, reconnect loops, and logging buffers. - Add or document a memory smoke test/regression guard if the cause is found. - Consider defensive limits or backpressure for any unbounded in-memory collections. ## Evidence available now Reported observation: jsignal reached approximately 90GB resident set size. More runtime details still need to be gathered: workload, uptime, platform, process arguments, logs, and whether RSS drops after idle or GC.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
docs/agents-checkout-hygiene
docs/agents-fj-cheatsheet
feature/jsignal-path-and-command
feature/agents-cicd-check
chore/local-mine-authority-agents-20260803
fix/update-jsqlite-revision
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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
ober/jerboa-signal#8
No description provided.