App crash with very large response

[foxontherock]

When I "GET" too much data, the app freeze for several seconds, then crash.
It looks like it is parsing the result to make it looks good on the "JSON" tab.
When I use smaller sets, I see when the app completes getting the data (not too long), and after, it freezes, then I see my data on the JSON tab.
But when the data is too large, it never finish, then crash.

Looks like "DOM" activity to create the beautiful treeview can sometimes be too complex.

May I suggest, if the resultset is too large, to switch to "raw" view, and just display "too much data" on the JSON tab, it will prevent crashing.

Or, add an option to set "Raw" as default result tab, and calculate "json" only when we change tab? (but that doesn't prevent from crashing when I hit "JSON" ...)

Expected outcome

See the data and not crash

Actual outcome

Crash when the resultset is too large

Versions

App: 9.14.64.305-stable Chrome: 58.0.3029.110 Platform: Windows (10)

Steps to reproduce

GET a lot of data from any json call.

[StephenCasella]

I've noticed this as well but if I switch the response view from JSON to Raw it unfreezes after a few moments. It also unfreezes if I navigate away from that request to another one in the project. Definitely seems related to parsing.

[jarrodek]

Thank you for the issue report(s). I wasn't able to reproduce this issue but maybe I was using to less JSON data. I'll play with it more. Since this module is scheduled for redesign it might be fixed soon.