-
-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with QuicCodecDispatcher #710
Comments
Can you also take a heap dump and share it ? |
Hi @normanmaurer , |
Hi @normanmaurer , |
Sorry these last few weeks been super busy. I will pick it up next week |
@poisonriver hmm... in the heap dump I only see 10 |
@poisonriver I am pretty sure this should fix what you did see #720 |
Hi @normanmaurer ,
|
@poisonriver keep me posted |
@poisonriver any updates ? |
Hi @normanmaurer |
Nope... PRs welcome :) |
PR is created |
Hi @normanmaurer ,
I'm trying to utilize
QuicCodecDispatcher
and noticed that a number ofQuicheQuicChannel
instances are increasing with time on my server (when http clients come and leave) thus creating a leak. I removedQuicCodecDispatcher
from the server initialization and the problem disappeared. Then I added logging forQuicChannel
init and Http3 request processing (Http3RequestStreamInboundHandler.channelRead
) and noticed the following:QuichChannel
init call happensQuichChannel
init calls happen, while Http3 request is being processed only in one of theseQuicChannel
s.My server initialization code is below, Wireshark screenshot are attached. Can you please advise if I'm missing something or there's some other issue?
The text was updated successfully, but these errors were encountered: