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
I'm curious to see other's thoughts here, but I am using Hogan.js in a stream processor and found that a recent update caused a memory leak, essentially every string ever processed was held in ram. I eventually tracked this to Hogan.cache.
I'm wondering if this could be a weak linked cache? Or what would people think if this was mentioned in the docs so that anyone else using it in a high-volume environment won't hit the same issue?
The text was updated successfully, but these errors were encountered:
I'm curious to see other's thoughts here, but I am using Hogan.js in a stream processor and found that a recent update caused a memory leak, essentially every string ever processed was held in ram. I eventually tracked this to Hogan.cache.
I'm wondering if this could be a weak linked cache? Or what would people think if this was mentioned in the docs so that anyone else using it in a high-volume environment won't hit the same issue?
The text was updated successfully, but these errors were encountered: