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
We think we found a memory leak in js-data-angular. We use it to populate a dashboard that our client keeps open 24/7. After some time the client's machine stopped responding and we determined the problem to be a memory leak which we traced to this library.
The heap size steadily increases over time while the number of cached objects remains the same. We think the original JSON array coming in is retained in memory, but we're not sure about that. The browser we tested with was Chrome.
The workaround for our application was to use Angular's $http to download the information and then inject it manually.
Ah yes, thank you - I was working from memory because we've been hunting for that bug yesterday. I remember we were trying different combinations of bypassCache and cacheResponse with findAll and refreshAll (though no combination helped), apparently things got mixed up a bit in my head :)
Activity
jmdobry commentedon Nov 13, 2015
Thanks for the link, I'll take a look
jmdobry commentedon Nov 13, 2015
Your demo uses a
skipCacheoption, but neither js-data nor js-data-angular have such an option.gregopet commentedon Nov 13, 2015
Ah yes, thank you - I was working from memory because we've been hunting for that bug yesterday. I remember we were trying different combinations of
bypassCacheandcacheResponsewithfindAllandrefreshAll(though no combination helped), apparently things got mixed up a bit in my head :)jmdobry commentedon Nov 13, 2015
refreshAll()is the same asfindAll(null, { bypassCache: true })