Internal issue 3143 - CPU usage jumps to 100% on version 3.14.0+
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 53
- Forks
- 63
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 15
Description
We have identified that when the attached code is run and the button is pressed, the CPU usage of the tab jumps to 100% and stays there if the version of {{@ukic/react}} and {{@ukic/web-components}} is at least 3.14. On earlier versions (3.13 or less) the code runs as expected.
The 100% CPU usage causes the tab to lock, and only return to functionality once the process is killed.
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 running the attached reproduction with @ukic/react and @ukic/web-components at version 3.14.0 or later, then compare it with version 3.13 or earlier. Trace the button-triggered behavior until the CPU loop is identified; done means the tab no longer reaches sustained 100% CPU and the reproduction works in the affected versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100