quic-go.newStream high memory usage about quic-go HOT 7 CLOSED

Previously, I used the v40 version and then upgraded to v44 and then discovered this error. I'm not sure if it was due to the v44 version because I didn't monitor it before.
And thank you, I have solved this problem already , it seems like the error was closing the stream without calling cancel write first. I changed the code to call cancel write before closing the stream and the memory problem was solved

from quic-go.

Probably fixed by #4523. Can you try out the brand new v0.44 release?

from quic-go.

Probably fixed by #4523. Can you try out the brand new v0.44 release?

seems unrelated, I don't use http3,

from quic-go.

How many connections are you handling? How many streams are open? What are the stream limits, both on your and on your peer's side?

This could be a totally expected behavior, or indicative of a memory leak. Without more information, we won't know which.

from quic-go.

I have tried to measure the following information

• 20k quic connection
• 70k stream open
• MaxIncomingStreams: 100000000

from quic-go.

profile (2).pb.gz
Go pprof profile. Can you give me some reasons why newStream is taking up a lot of resources so I can check again if my code is affecting it?

from quic-go.

You could try running your app with quic-go v0.42. We made some minor changes to the stream state machine in v0.43 and v0.44, maybe that introduced a bug.

To be honest, I'm not sure if the memory consumption you're seeing is that unusual though. You're handling a lot of streams after all. In your code, make sure to properly close both sides of the stream, and to not keep references to closed streams around, so that the stream can actually be garbage collected.

from quic-go.