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 was pointed there by heap profiler, as I was investigating an out of memory error in a development pipeline with a long-running analysis task (which uses split in localhost mode).
As you mentioned, onFullQueue callback is never set in localhost mode, leading to memory usage growing unboundedly.
We have released a new version of @splitsoftware/splitio-commons with a fix, and upgraded it in our Javascript SDK v10.22.3. The approach we followed is to not keep in memory the events and impressions generated by calling the track and getTreatment* methods, if the SDK factory is in localhost mode.
Activity
hbqdev commentedon Dec 15, 2022
HI @raoz
We are reviewing this issue with our engineering team.
Thank you and Regards
EmilianoSanchez commentedon Dec 16, 2022
Hi @raoz ,
As you mentioned,
onFullQueuecallback is never set in localhost mode, leading to memory usage growing unboundedly.We have released a new version of @splitsoftware/splitio-commons with a fix, and upgraded it in our Javascript SDK v10.22.3. The approach we followed is to not keep in memory the events and impressions generated by calling the
trackandgetTreatment*methods, if the SDK factory is in localhost mode.Thank you
Update InLocalStorage to avoid memory leak in localhost mode (#181)