Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Performance & Memory Optimisations #529
referenced this issue
Oct 10, 2013
Have been looking at docpad heap snapshots for the past day or so and found something I wanted to share with others.
In some circumstances coffee-script will instantiate your classes as "ctor" instead of the actual defined class name. (see here for more jashkenas/coffeescript#3236)
I have a very large docpad instance where there is around 16mb across 4644 ctor classes.
Here is a sample of class names in docpad heaps that like to lead a second life called "ctor"
To determine the real class behind the ctor class you can look at the ctor.constructor or the ctor.proto.constructor
So as a heads up when looking at a docpad heap snapshot make sure you also visit the ctor class. This will contain some very import class instances.
disclaimer: i'm not suggesting that ctor is introducing memory leaks. All I know is that it introduces confusion in the heap.