User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0

Steps to reproduce:

• Open video page
  https://www2.camara.leg.br/camaranoticias/tv/embedAoVivo.html

• Inspect request media parts

• Break the stram

Actual results:

Stream stopped

Expected results:

Inspect parts of stream stop the stream play.

Thank you for your bug report! I'm sorry, I'm having some trouble understanding your steps to reproduce. It sounds like you're having a problem with using the devtools to inspect the page, but I'm not sure exactly where the problem is. Could you please add some more detail and perhaps a screenshot, so I have a better idea of what you are trying to do?

I tried the video stream, but the playback pauses and buffers frequently for me, which makes it difficult to tell if I'm seeing what you are seeing.

[:dminor] Whein you try to inspect the Body of the requests in the network tab(Developer Tools) the stream pause and the browser have a slow down. Try to open the stream and inspect the body of TS video parts from Network tab of Developer Tools.

Thanks

[:dminor] When you try to inspect the Body of the requests in the network tab(Developer Tools) there is a video stream play pause and the browser have a slow down.

Try to open the stream and inspect the body of TS video parts from Network tab of Developer Tools.

Thanks

Thank you for the extra details. I'm not sure if this a playback bug or a devtools bug, Bryce, what do you think?

My inclination would be towards this being a devtools bug/enhancement. Inspecting the response body in leads to the devtools trying to display a large amount of binary content, which is going to require some resources.

When I try this I see my UI jank/freeze, but the video remains playing most. A profile during UI janks: https://perfht.ml/2NO1dwu indicates we're doing a lot of time rendering the UI.

I'm going to move this over to devtools. It's not clear to me if this is a network tab specific issue, or (I think more likely) a general problem with rendering large amounts of text, but hopefully this finds its way to the right person.

Wellington, would you be able to capture a profile via:

• Enable the profiler icon in nightly from Tools -> Web Developer -> Enable Profiler Toolbar Icon.
• An hourglass icon should show up on your toolbar.
• Click on that icon and start the profiler before reproing the bug.
• Click the capture profile button after reproing.
• Publishing the profile and linking it in this bug.

I suspect we'll see a similar profile to mine, but it would be useful to confirm.

[:bryce] I will try to do the steps you informed.
And I will post the result as soon as possible.

Thanks!

The Profiler output: http://bit.ly/2JI3FQ2 (https://profiler.firefox.com/public/107f914099e289514b4c64aa6020ffb71fe86698/calltree/)

Thanks. My read on that profile is consistent with comment 5. Let's see if someone more familiar with the dev tools has more insight.

The priority flag is not set for this bug.
:Honza, could you have a look please?

For more information, please visit auto_nag documentation.

Does this work in Chrome? It seems, apart from the hang in Firefox, Chrome and Firefox wait for the stream to be completed to show the response.

Hi,

Working very well at chrome.. and very fast!

The binary output is strange, but is it expected.
I tested again in Firefox and the problem still occurring.

Last testes site:
http://www.sbtinterior.com/aovivo/

Thanks

Ts file example... The chrome can see response...
The firefox can't and truncate the content.

Just clarifying what works and doesn't – thanks a lot for your help debugging this!

Ts file example... The chrome can see response...

The response shows up in Chrome after the stream is completed but while the connection isn't closed yet. When I throttle the connection to Slow 3G in Chrome, the response does not show up while it is still downloading. Is that what you see?

Please see the question in comment #13

(In reply to :Harald Kirschner :digitarald from comment #13)
Hi,

I think the question is the Chrome can work fine with binary content, specially large videos parts.
My problem in firefox is: In large request the firefox can't be stable when response tab is selected.

My question is: why the performance is very poor at firefox in response debugging in comparison with Chrome?
And my problem is: The browser start to be verry slow and sometimes crashed...
Se second detail is: The browser slow down the computer too.

Sorry my English...

Thanks!

(In reply to Bryce Seager van Dyk (:bryce) from comment #5)

I liked very much the Bryce description.

And the only difference with my scenario is my stream stopping.
Maybe because my PC resources is poor. Maybe breaking the flow of the streaming or network.
But I can't tell exactly.

Thanks!

Agreed, lets focus this bug on the severe hang that inspecting a stream causes.