[GH-ISSUE #5886] [bug]: Browser Freeze When Handling Large Variable Content in Hoppscotch #2316

New issue

Open

opened 2026-03-16 23:56:00 +03:00 by kerem · 1 comment

kerem commented

2026-03-16 23:56:00 +03:00

Owner

Originally created by @iDschepe on GitHub (Feb 17, 2026).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5886

Is there an existing issue for this?

I have searched existing issues and this bug hasn't been reported yet

Platform

Web App

Browser

Chrome

Operating System

Windows

Bug Description

Bug: Browser Freezes When Handling Large Variable Content

Description

When a variable in Hoppscotch contains a very large text value, the application initially remains responsive and usable. However, certain actions consistently cause the browser to freeze for an extended period.

Steps to Reproduce

Create or import a variable containing a very large text payload.
Open the Variables tab.
Attempt to edit either:
- The variable name, or
- The variable content.
OR
With the large variable present, send any request (e.g., while the active view is the Body tab).

Expected Behavior

Editing variable names or values should remain responsive.
Sending a request should complete without significant delay or UI blocking.

Actual Behavior

The browser freezes completely.
The UI becomes unresponsive for approximately one to several minutes.
After the freeze period, the request is eventually sent.

Impact

Severe usability degradation when working with large variable values. The application becomes temporarily unusable and blocks normal workflow.

Additional Information

A reproducible test case (importable configuration) and the exact variable content will be provided separately.

Test.json
htmlContent-var-sample.txt

Deployment Type

Hoppscotch Cloud

Version

No response

Originally created by @iDschepe on GitHub (Feb 17, 2026). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5886 ### Is there an existing issue for this? - [x] I have searched existing issues and this bug hasn't been reported yet ### Platform Web App ### Browser Chrome ### Operating System Windows ### Bug Description # Bug: Browser Freezes When Handling Large Variable Content ## Description When a variable in Hoppscotch contains a very large text value, the application initially remains responsive and usable. However, certain actions consistently cause the browser to freeze for an extended period. ## Steps to Reproduce 1. Create or import a variable containing a very large text payload. 2. Open the **Variables** tab. 3. Attempt to edit either: - The variable name, or - The variable content. **OR** 4. With the large variable present, send any request (e.g., while the active view is the **Body** tab). ## Expected Behavior - Editing variable names or values should remain responsive. - Sending a request should complete without significant delay or UI blocking. ## Actual Behavior - The browser freezes completely. - The UI becomes unresponsive for approximately one to several minutes. - After the freeze period, the request is eventually sent. ## Impact Severe usability degradation when working with large variable values. The application becomes temporarily unusable and blocks normal workflow. ## Additional Information A reproducible test case (importable configuration) and the exact variable content will be provided separately. [Test.json](https://github.com/user-attachments/files/25367955/Test.json) [htmlContent-var-sample.txt](https://github.com/user-attachments/files/25367954/htmlContent-var-sample.txt) ### Deployment Type Hoppscotch Cloud ### Version _No response_

kerem added the

bug

need testing

labels

2026-03-16 23:56:00 +03:00

kerem commented

2026-03-16 23:56:10 +03:00

Author

Owner

@hervekom37 commented on GitHub (Feb 18, 2026):

This looks like a UI blocking issue caused by rendering very large variable payloads in the browser.
As a workaround, storing large content externally or referencing files instead of inline variables may help.
Some teams handling large payload testing use Apidog, which processes large bodies without freezing the UI.

@hervekom37 commented on GitHub (Feb 18, 2026): This looks like a UI blocking issue caused by rendering very large variable payloads in the browser. As a workaround, storing large content externally or referencing files instead of inline variables may help. Some teams handling large payload testing use Apidog, which processes large bodies without freezing the UI.

kerem referenced this issue

2026-03-17 01:19:02 +03:00

[PR #2316] [CLOSED] chore(deps): bump @codemirror/lint from 0.19.6 to 0.20.2 #3729