https://github.com/simonihmig/e-cp-v-memleak

https://github.com/simonihmig/e-cp-v-memleak

Last synced: about 2 months ago
JSON representation

• Host: GitHub
• URL: https://github.com/simonihmig/e-cp-v-memleak
• Owner: simonihmig
• Created: 2018-02-22T20:24:28.000Z (over 7 years ago)
• Default Branch: master
• Last Pushed: 2018-02-22T20:24:42.000Z (over 7 years ago)
• Last Synced: 2025-03-29T02:08:22.703Z (2 months ago)
• Language: JavaScript
• Size: 148 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# e-cp-v-memleak

Reproduction of a memory leak issue in `ember-cp-validations: https://github.com/offirgolan/ember-cp-validations/issues/485

## Not leaking

The simple `no-leak` component does not use a validation mixin. And visiting a page with this component and going 

somehwere else does not cause a memory leak. Steps to reproduce:

* Run the 'no leak' acceptance test

* Create a heap snapshot in Chrome

There is no `Container` instance left:

![noleak](docs/noleak.png)

## Memory leak

The  `memory-leak` component *does* use a validation mixin. And visiting a page with this component and going 

somehwere else causes a memory leak. Steps to reproduce:

* Run the 'leak' acceptance test

* Create a heap snapshot in Chrome

There is a `Container` instance left:

![leak](docs/leak.png)

Also you can see the component instance (ES6 class `MemoryLeak`) not being GCed:

![leak2](docs/leak2.png)