Rasool Ziafaty
Rasool Ziafaty
Did you find any solution? @remotejob
@AlessandroSechi did you find any solution?
@Marreck did you find any solution for this?
this is a qlog connection tracer : ``` quicConf.Tracer = func(ctx context.Context, p logging.Perspective, connID quic.ConnectionID) logging.ConnectionTracer { filename := fmt.Sprintf("/tmp/server_%x.qlog", connID) f, err := os.Create(filename) if err != nil...
Thank you for your response. After upgrading to v0.35.1, I have observed that the memory usage of my application keeps increasing over time and does not get released, eventually consuming...
I understand that identifying the specific release causing the memory leak might be challenging due to the significant jump in versions. To provide more helpful information, I will conduct further...
Thank you for your suggestions. I will test the latest v0.34 release tomorrow to see if the memory leak issue persists. Regarding the tracer, I have also tested without any...
I have tested the application with the v0.34 release as suggested, and unfortunately, the memory leak issue still persists. The memory consumption continues to increase over time, eventually consuming all...
I switched from v0.34.0 to v0.33.0 to investigate the memory leak issue. I will proceed with testing the application using v0.33.0 and monitor the memory consumption. I will provide further...
@marten-seemann I have exciting news to share regarding the memory leak issue. After switching to v0.33.0 of github.com/quic-go/quic-go, I am pleased to inform you that the memory stability has significantly...