Closed pozylon closed 6 years ago
As you noted, I haven't received any reports of memory leakage in job collection until now. But I would clearly need much more information than you provide to be able to reproduce what you are seeing and try to help track down whether the perceived leak is real or a consequence of delayed GC. If it is real, then of course it still wouldn't be immediately clear that job-collection itself is the culprit.
If you'd like to proceed, please create and share a github repo and instructions to reproduce the results in the screenshot above, and I'll be happy to take a look.
We run several Meteor programs that utilize JobCollection 24/7 on dozens of windows clients and we have not noticed any lasting performance issues or memory leaks, just my two cents.
Hi there
I guess meteor job collection leaks memory over time, but I'm wondering why there is no issue posted here yet. Nobody else?
Look at the screenshot here: the only difference is crossiety-one doesn't startJobServer() whereas crossiety-two does.
What I've found out so far:
Things to try: