You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My app had a memory leak and would go from 130mb to 512 over a couple hours and then crash. After commenting out the code for node-loggly, the memory no longer climbs.
I used it as:
varLogger=newLoggly({token: "<token>",subdomain: "<subdomain>",auth: {username: "<username>",password: "<password>"},tags: ["customer_purchase"],json: "true"});// a bunch of log statements in various parts of the codeLogger.info('no products in'+storeData._id);
I have about 700 logs per minute in bursts every 5 seconds.
If it helps, I am using the meteor package miktam:loggly which is a wrapper around node-loggly.
The text was updated successfully, but these errors were encountered:
@zodern do you have any update about your memory leak issues? can you confirm that it was the loggly package that caused it? we are using it and also have a memory leak that climbs steadily to 512mb before dropping down a bit …
My app had a memory leak and would go from 130mb to 512 over a couple hours and then crash. After commenting out the code for node-loggly, the memory no longer climbs.
I used it as:
I have about 700 logs per minute in bursts every 5 seconds.
If it helps, I am using the meteor package miktam:loggly which is a wrapper around node-loggly.
The text was updated successfully, but these errors were encountered: