Skip to content

Memory leak on frequent updates #345

Open

Description

@gregopet

Hello,

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.

I've put together an example here: http://razum.eu/memoryleaktemp/index.html

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.

Activity

  1. jmdobry commented on Nov 13, 2015

    @jmdobry
    Member

    Thanks for the link, I'll take a look

  2. jmdobry commented on Nov 13, 2015

    @jmdobry
    Member

    Your demo uses a skipCache option, but neither js-data nor js-data-angular have such an option.

  3. gregopet commented on Nov 13, 2015

    @gregopet
    Author

    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 :)

  4. jmdobry commented on Nov 13, 2015

    @jmdobry
    Member

    refreshAll() is the same as findAll(null, { bypassCache: true })

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions