Termix-SSH / Termix-SSH/Support
[BUG] node-MainThread
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 28
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Title
Process is using up 100% CPU, 17.8gb VIRT, running for 78+ hours, causing spikes in load avg
Platform
Website - Chrome
Server Installation Method
Docker
Version
2.7.1
CLI Installation Method
None
CLI Version
No response
Troubleshooting
- I have examined logs and tried to find the issue
- I have reviewed opened and closed issues
- I have tried restarting the application
- I have checked open issues and ensured this is not a duplicate
The Problem
Ever since upgrading Termix from 2.6.0 to 2.7.1, I have noticed overall slowness of the system. Running "top" I am seeing the culprit is the process node-MainThread, running for 78+ hours, using 17.8gb virtual memory, and 100+% CPU, with load averages of 1.20-2.80.
How to Reproduce
Just trying to use the system.
Additional Context
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the node-MainThread behavior in the Docker installation on Termix 2.7.1, comparing it with 2.6.0 while monitoring CPU usage, virtual memory, and load average. The issue does not name source files or tests; done means identifying the regression and confirming that normal use no longer causes sustained 100% CPU or rapidly increasing memory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, node.js
- Domain
- backend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100