Closed hoIIer closed 2 years ago
I agree! I would also be happy to have more details on the exact approach when dealing with the new test style. If possible also with a current Chrome Dev Tools version. Would really appreciate that!
@erichonkanen how did you finally manage to find the leak?
Hey so I just discovered this and upon doing a heap snapshot of an integration test for a very simple component that uses the new style of tests, I discovered that it has 4 references to
Container
. When I open up a single one of those, I am quickly lost and have no idea what to look for. Some of the nodes in the graph expand to a huge number of objects that are deep within some part of the code.How can I learn more about how to identify what to look for or find out why a reference to a container is being kept and make use of this? What are the ramifications of 4 references?
Here is the component for the integration test:
Here is the top 1/3 of the integration test file (cut out the other 2 tests):
PS I just added 3 acceptance tests to our app that previously had none and our ci server exploded when the max of 3GB memory was hit during build of the ember app... when I do the same process described in example 1 of this repo applied to
ember t -f acceptance -s
, I get 7 references toContainer
:I don't know enough to diagnose but this is worrying me as this repo already stated even 1 reference is bad.