1577098 - Big response body rendering is slow

Status: RESOLVED DUPLICATE of bug 1127077

(DevTools :: Netmonitor, defect, P3)

Description

[repe]

Attachment: 2019-08-28_08h07_12.png

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3809.100 Safari/537.36

Steps to reproduce:

call a web service that returns a 2.21MB json response

Actual results:

the response got truncated see image attached

Expected results:

I expected to see the full response as it happens in order to smaller responses.

at least I expected to have access to the raw response no prettified one

at least even if truncated be able to copy the full raw response and paste on another software that can handle it

Comment 1

[repe]

after year on chrome, I was really enjoying firefox but at the moment I'm developing with big responses everywhere so until this is fix I'm forced to go back to the ram eater (eats ram like the cookie monster eats cookies but it shows the response ;-)).

Comment 2

[Andrei Purice]

Hello,

Can you give us the exact web service used in order to reproduce this issue?

Comment 3

[repe]

Hello,

For instance, any JSON response over 1mb of size will do, but I added to my git hub account a public repo with a file you can download as raw on https://raw.githubusercontent.com/renatofsp/json/master/bigJson.json.

If we make a get request to https://raw.githubusercontent.com/renatofsp/json/master/bigJson.json with firefox response is truncated.

I have a look around and went into about:config and increased devtools.netmonitor.responseBodyLimit value but then firefox just crash when trying to precess it on the dev tools.

Comment 4

[repe]

• process not precess sorry for the typo

Comment 5

[Andrei Purice]

I have tested this issue and could reproduce it on Windows and Macos on all versions release 68.0.2, beta 69 and Nightly 70.0a1 (2019-09-01).
I have set a component for this issue as well, however if you feel like it's not the correct one please feel free to change it.

Comment 6

[repe]

Attachment: firefoxVersion.png

Comment 7

[repe]

It's fine thank you.

I was a bit dumb since I could have added the os and firefox version
os: windows 10 64 bits
firefox: on the previous comment

Comment 8

[Kershaw Chang [:kershaw]]

I think this is a devtool issue.

Comment 9

[Jan Honza Odvarko [:Honza] (always need-info? me)]

@repe: this is a feature, we limit the size of the rendered response to avoid memory and performance troubles.
However, you can change the size in about:config

devtools.netmonitor.responseBodyLimit is set to 1048576 by default.
You can just change the value and restart Firefox.

Does that help?
Honza

Comment 10

[repe]

@Honza it helps in a way.

I had done that already but the best thing will be to be able to see the response without the performance issues if I increase the limit let say to 2.5MB it starts to crash firefox so I can't see the response either way ;-).

if its a feature that's fine no worries I can live without it.

Comment 11

[Jan Honza Odvarko [:Honza] (always need-info? me)]

Yeah, it's known perf issue. I'll keep this one open so, it isn't forgotten.

Honza

Comment 12

[:Harald Kirschner :digitarald]

Work continues in bug 1127077.