mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #1890] UI Hangs when fetching "big" response #601
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#601
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 @demfabris on GitHub (Oct 19, 2021).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/1890
Big responses hangs the UI. It doesn't completely freeze but it turns out to be unusable.
This happens either as PWA or in the browser
Steps to reproduce the behavior:
Expected behavior
UI should warn that the payload is too big to display and not hang
Screenshots

Desktop:
@liyasthomas commented on GitHub (Oct 20, 2021):
Do you have an estimate of the response size which resulted in hang.
@demfabris commented on GitHub (Oct 20, 2021):
Yea it is about right. ~200kb
@liyasthomas commented on GitHub (Oct 20, 2021):
Thanks for providing the details. We'll look into our supporting libraries and see if there's any issues with responses of this size. Anyway will introduce an apt prompt if it exceeds the limit.
@liyasthomas commented on GitHub (Nov 15, 2021):
We've updated the CodeMirror editor (the library which we use in Hoppscotch) to v6. This has bought several performances boost to the render engine and now handles responses with more than 200kb. Hence closing.