Closed bloudermilk closed 10 years ago
yeah, this leak murdered my workers last night. i'll be moving to node-apn until this is sorted out.
New release is up which had some outstanding PRs merged that might have dealt with this. If you could try it out and see and let me know how I goes, I would greatly appreciate it. Thanks.
My RAM usage seems to have normalized using the new release. I'll let you know if anything changes.
Not seeing any leaks as of 1.1.3
Fantastic, thanks for the update.
@logicalparadox no problem. I'm running 1.1.3 now so I'll try to close out old issues if they don't crop up again.
I'm seeing consistent memory leaks in our apnagent process. We're running two clusters of 4 express servers / apnagents and after a few hours they both exceed Heroku's memory cap of 512 MB. I can confirm that during the same period, the cache and queues are staying around the same size. I'm running with a 30s cache ttl.
I'm fairly confident that the leak isn't in our application code, since it's really a dead-simple express app that only interacts with apnagent. That said, I'm hoping to reproduce and trace the leak on my dev machine soon.