Replies: 4 comments 2 replies
-
Not a leak, you're just not giving the event loop any time to do actual work. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Sorry, what work? I'm scheduling next tick after the request has completed, no ? |
Beta Was this translation helpful? Give feedback.
0 replies
-
I just tried replacing next_tick with $IOLOOP->timer (0.01 => sub { ua_test_1 ($host, $port) }); Memory usage still increases, but more slowly. |
Beta Was this translation helpful? Give feedback.
1 reply
-
Upgraded to perl 5.24 and it's not happening anymore! |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Steps to reproduce the behavior
UserAgent leaks, here's a minimal example:
Expected behavior
Memory usage should remain steady while this script is running.
Actual behavior
Memory reported by top (the
VIRT
column) steadily increases by approx 20 KiB per second.Note that the example above doesn't involve self-referencing closures - AFAICT - so it can't be that.
Beta Was this translation helpful? Give feedback.
All reactions