New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Memory leak #555

petronellius opened this Issue Dec 21, 2016 · 0 comments


None yet
3 participants

petronellius commented Dec 21, 2016

I'm submitting a bug report

  • Library Version:

Please tell us about your environment:

  • Operating System:
    Windows 10

  • Node Version:

  • NPM Version:
  • JSPM OR Webpack AND Version
    JSPM 0.16.47
  • Browser:
    Chrome 55.0.2883.87

  • Language:
    TypeScript 2.0

Current behavior:
Minimal demo:
skeleton-typescript -

Steps to reproduce:

  1. Open Aurelia skeleton in browser and navigate to Memory leak tab
  2. Take a Heap snapshot in Chrome Developer Tools Profiler
  3. Click Delete button which remove one cell (aurelia custom element).
  4. Take a Heap snapshot in Chrome Developer Tools Profiler and choose Comparison view
  5. In Comparison view you can see that one cell object was added and none was deleted.


If I remove one of the nested divs or remove value binding on cell component I get expected result - one cell object was added and two were deleted.


Expected/desired behavior:

  • What is the expected behavior?
    Cell components that are not attached to DOM anymore should be released.

  • What is the motivation / use case for changing the behavior?

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