Adam Gastineau

@AntonioVentilii it would be very helpful if you could provide a minimal repro. While the crash is obvious (thus my PR), we really need to understand why this is happening...

Closing due to lack of concrete repro. Please feel free to open a new issue if you find some minimal reproduction of this issue.

@ScarletMcLearn at what point specifically are you experiencing the OOM? Simply running your login test over and over does increase memory consumption, but it doesn't crash in any short amount...

After studying a number of traces it's unclear if there's actually a leak here. There's definitely work we can do about loading only subsets of traces to prevent overloading Chrome,...

Closing due to lack of concrete reproduction. Please open a new issue if you are able to reliably and minimally reproduce this issue.

As I suspected in your sample code, the issue lies in the line: ```python await context.route("**/*", lambda route, request: route.continue_(url=request.url)) ``` specifically ```python route.continue_(url=request.url)) ``` URL fragments (the URL hash)...

I'm sorry, you're right. Firefox will drop the fragment when a route intercepts the message, but Chromium and WebKit do not.

Makes sense. Things have been stable for quite a while.

I am also encountering this issue. Logging around the `install` method indicates its hanging inside of `std::io::copy`, so the writer is not allowing the flow to continue, probably because it's...

Please break this down into individual cases that we can run and evaluate each scenario. Without a full, minimal repro we are unable to help.