Running out of CPU inside of containers
Open
Nobody has claimed this yet.
Type: Bug
- Dominant language
- TypeScript
- Stars
- 1.5k
- Forks
- 228
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 48
Description
When running inside of a container with an input file of 2.5M, I am experiencing that redocly just hangs while running CPU% to 100%. Was wondering if there's any chance that this is because of some node dependencies that are particularly CPU intensive...?
No .redocly.yaml file used for this build.
Redocly version: 1.12.2
Node version: 20.12.2
Contributor guide
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 hang inside a container with the reported 2.5M input, Redocly 1.12.2, and Node 20.12.2; no source files or tests are named. Done means establishing whether CPU saturation is reproducible and identifying the affected CLI behavior or dependency.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, typescript
- Domain
- cli, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100