Memory Leak?

[zepumph]

from code review #30

I fuzzMoused three separate times for over an hour each time the memory increased over 10MB. I don't know if that is large enough to warrant the title of "leak" but it wasn't tapering off, so I thought it warranted an issue to discuss.

The following showing a fuzzRate of 3000 for an hour (it starts at 50MB because I had a caching problem resolved in #70 ):

[pixelzoom]

Heap comparison?

[zepumph]

Still quite unsure about how to read them. I didn't find anything obvious that was mentioned during @jessegreenberg and my recent briefing by @jonathanolson. Would you mind calling to share screens for it. I think there is still a lot to learn about what to look for.

[pixelzoom]

Would you mind calling to share screens for it. I think there is still a lot to learn about what to look for.

Unlikely before Monday.

[zepumph]

Ok I'll see what I can do.

[zepumph]

With a fuzzRate of 5000, I let it go for 2 hours, and here are the heap sizes.

It seems like it really tapered off at about 11MB. It took a long time to taper off, I'm not sure what that means. In the heap comparisons nothing really stood out to me. most deltas were in the Array and Object top level rows. Here is an example of a comparison.

[zepumph]

After continuing that same tab this morning for multiple hours, I see that it did level off. Closing this issue, there isn't a memory leak.