Utility: Network Service

[Luke Curley]

Hey all,

I'm running my QuicTransport application on Chrome 85 and noticed a performance issue. "Utility: Network Service" uses a constant 99.9% CPU.

My application receives a constant stream of data and doesn't appear to be starved. Reducing the data rate doesn't make an impact and killing the task closes the QuicTransport connection. My guess would be a busy loop somewhere in the QuicTransport networking code.

[Yutaka Hirano]

Oh, thank you! Could you file a bug and attach a tracing log?

--
You received this message because you are subscribed to the Google Groups "web-transport-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to web-transport-...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/web-transport-dev/CAHVo%3DZmOnfv%2Bd2upe7dzJ3ofofFJM2%2Bj%3DwSw9pzuFUpwBuvrew%40mail.gmail.com.

[Luke Curley]

Hey Yutaka,

I filed issue 1129597 with a trace and a test case. 

My test case is to have the server open a stream, write "ping", and leave the stream open. Network service uses a full CPU core and the text "ping" is not flushed to the application (separate issue). There may be other ways to reproduce but this one is pretty easy.

We've been able to work around the other bugs found thus far but this is the first blocker. Can you keep me updated on roughly when the fix could be available so we can plan our internal experiment?

Thanks again!

[Victor Vasiliev]

I just tested it in the latest release of Chrome Canary, and it appears that the test example you've linked no longer causes the Network Service to spin.  Thanks for reporting this!

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/web-transport-dev/CAHVo%3DZnBdW6gJ%2BZByT6GzonPJ8LGWsq3UTHpb-o30WeHCmtvXQ%40mail.gmail.com.

[Luke Curley]

I can confirm that it's fixed now. Thanks Yutaka!