Memory leak when HTTP3 is enabled

[julien-duponchelle]

We've identified a memory leak that occurs when calling the /forward endpoint in version 1.11.0 and later. The issue is inconsistent, and we haven't yet been able to create a reproducible scenario. We've also observed that once the memory grows, it's never released, even after several hours.

We have, however, observed that the leak does not occur when the disableHttp3 flag (introduced in version 1.11.2) is enabled.

Do you have any insights or known issues related to this behavior? I'm sorry if the report is not more accurate, I would have prefer to be able to provide a way to reproduce.

[bogdanfinn]

@julien-duponchelle can you share maybe a bit more information what kind of requests (GET / POST and other information) are you doing, are you working with multiple sessions or not and in which frequency you are sending requests?

[julien-duponchelle]

It’s a mix of GET and POST requests running in parallel. The requests are standard HTML pages and JSON APIs (no binary content). The setup also uses proxies, which can sometimes be unreliable.

There’s no session handling involved.

I currently have two theories about the leak:

• It happens when hitting a specific type of website.
• It happens when an error occurs.

If you have any scenarios in mind that I could test locally, I’d be happy to try them out and share the results.

I realize this report isn’t very actionable yet, it’s more of a "message in a bottle" in case someone else encounters the same issue and we can debug it together.