mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #5516] [bug]: The interface returned a 0.3MB tree structure, with CPU usage hitting 100% and the entire page freezing. #2125
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#2125
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @zhaoqiang1024 on GitHub (Oct 27, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5516
Is there an existing issue for this?
Platform
Desktop App
Browser
Chrome
Operating System
macOS
Bug Description
The interface returned a 0.3MB tree structure. After selecting the result, the CPU utilization hit 100%, causing the entire page to freeze.

Deployment Type
Hoppscotch Cloud
Version
No response
@mio9 commented on GitHub (Oct 31, 2025):
I can confirm this one, this happens even when the response is not large at all, the CPU usage spikes up to 100% for a few seconds
@lostars commented on GitHub (Nov 14, 2025):
Same here, large json will cause memory leak, the latest version (25.10.1) will cause all cpu cores full loaded everytime it send a request and recover when request completed.
macOS 15.7.2
@JohnICB commented on GitHub (Dec 23, 2025):
It is also happening in
v2025.11.2using the self hosted version (macOS 26.2 (25C56))Sometimes the UI crashes and it goes blank and unresponsive. The workaround is to close and reopen and it will work fine for a while.
and the
app://process seems to crash, but the rest still remainDoes not seem to be impacted by size of request or response.