-
Notifications
You must be signed in to change notification settings - Fork 1
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
Memory Leak #6
Comments
Well with only two rules At and Null we start with Virt 271 Res 83344 (worker) and after two hours we have Virt 271 Res 84672 (worker) So there is a leak there someplace will see if I can track it down |
So did a few thing trying to find this yesterday not much luck. lib/Replay/DelayedEmitter.pm but not sure that helped at all |
Well I added weak_ref => 1,on a number of Replay.pm attributes and it died when replayd starts. Now working by taking one at a time off will see if the latest incarnation works or leaks |
What came of this troubleshooting? Did you find a patch for DelayedEmitter without looping references? |
Well will have to look a little deeper. Seem the cargotel code is leaking as well I will focus on getting a flat replay (no cargotel rules) running without leaking. I will use you latest branch and go on from there. SO far from what I have seen when you do something like this $self->emit( it can't release the 'Replay::Message::Timing' message me thinks. Well have to start the very laborious porcess |
Some place there is a slow memory leak in the code
Had replay up and running using replayd with 1 worm and 3 workers
Memory started with
Virt 561 Res 316 (worker)
Virt 561 Res 316 (worker)
Virt 561 Res 316 (worker)
Virt 561 Res 316 (worm)
now after 12 hours have
Virt 654 Res 404 (worker)
Virt 629 Res 381 (worker)
Virt 624 Res 379 (worker)
Virt 574 Res 328 (worm)
This was with a full rule suite but on the system but no little if any emits to Origin by clients.
Will try without rules to see what happens
The text was updated successfully, but these errors were encountered: