|
Welcome the channel on the development of Cro, a set of libraries for building reactive distributed systems, lovingly crafted to take advantage of all the Raku Programming Language has to offer (cro.services). This channel is being logged for historical purposes. Set by lizmat on 24 May 2021. |
|||
|
02:29
japhb left
03:58
japhb joined
08:32
AlexDaniel left
08:35
AlexDaniel joined
|
|||
| Geth | ¦ cro-http: Altai-man assigned to jnthn Issue docker image? github.com/croservices/cro-http/issues/149 | 10:51 | |
|
11:33
xinming_ joined
11:35
xinming left
13:06
xinming_ left
19:00
Altai-man left,
perlmaros left,
jnthnwrthngtn left,
perlmaros joined,
jnthnwrthngtn joined,
Altai-man joined
19:46
nine joined
19:49
xinming joined
|
|||
| nine | Did You Know...? That using Cro::HTTP::Middleware::RequestResponse's response processing leaks memory like crazy? | 19:51 | |
| Cro::HTTP::Middleware::Response however does not | 20:01 | ||
| It seems to be the mere tapping of $connection-state.early-responses that starts the leak. Even though AFAICT nothing's ever emitted from it. | 20:08 | ||
| Oh, no it's not the tapping. It's the additional whenever in the supply created by Response's transformer method | 20:10 | ||
| Yeah, I can replace it with a whenever Supply.interval(1) { } and it will still leak. Remove that whenever block and the leak vanishes. | 20:12 | ||