Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Insomnia becomes unusable when a request contains highly nested JSON #4890

Open
1 task done
loop-evgeny opened this issue Jun 23, 2022 · 1 comment
Open
1 task done
Labels
B-bug Bug: general classification B-performance Bug: performance issues S-unverified Status: Unverified by maintainer

Comments

@loop-evgeny
Copy link

loop-evgeny commented Jun 23, 2022

Expected Behavior

Insomnia is usable for any input text.

Actual Behavior

With highly nested JSON as input Insomnia uses 100% CPU for a while, then the entire window goes black and nothing can be done except to close it:

image

Even after restarting Insomnia it's unusable, because it automatically opens the last request and goes back to the same state!

Reproduction Steps

Create a new request, set input type to JSON and paste the contents of very-nested.json.txt into the textbox.

Is there an existing issue for this?

Additional Information

I worked around it by editing "%AppData%\Roaming\Insomnia\insomnia.Request.db" in a text editor to delete the request.

Insomnia Version

2022.4.2

What operating system are you using?

Windows

Operating System Version

Windows 7 x64

Installation method

https://insomnia.rest/download

Last Known Working Insomnia version

No response

@loop-evgeny loop-evgeny added B-bug Bug: general classification S-unverified Status: Unverified by maintainer labels Jun 23, 2022
@filfreire filfreire added the B-performance Bug: performance issues label Jun 23, 2022
@filfreire
Copy link
Member

Hi @loop-evgeny thanks for reporting this!

We're gathering info on all issues related with Insomnia handling large files, and the team will be doing some spikes to try and investigate and fix the lag issues in the coming months, we'll try to update here if there's any news.

In the meantime feel free to report any other issues you find.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
B-bug Bug: general classification B-performance Bug: performance issues S-unverified Status: Unverified by maintainer
Projects
None yet
Development

No branches or pull requests

2 participants