Skip to content
This repository has been archived by the owner on Apr 22, 2023. It is now read-only.

memory leak ... somewhere #16

Closed
fictorial opened this issue Jul 22, 2009 · 2 comments
Closed

memory leak ... somewhere #16

fictorial opened this issue Jul 22, 2009 · 2 comments

Comments

@fictorial
Copy link

There's excessive memory growth over time. It seems like there is some leak but I cannot find anything with ./configure --debug and valgrind.

This issue was originally raised here:
http://groups.google.com/group/nodejs/browse_thread/thread/a8d1dfc2fd57a6d1
@fictorial
Copy link
Author

This seems to have been resolved.

@ry
Copy link

ry commented Jul 28, 2009

fixed in 50c0d16

@fxfred fxfred mentioned this issue Apr 11, 2012
Closed
@Debbio Debbio mentioned this issue Jun 13, 2012
Closed
@barteksiudak barteksiudak mentioned this issue May 1, 2013
Closed
@mrjoes mrjoes mentioned this issue May 22, 2013
Closed
@DominicBoettger DominicBoettger mentioned this issue Jun 3, 2013
Closed
@cscott cscott mentioned this issue Mar 14, 2014
Closed
@migounette migounette mentioned this issue May 14, 2014
Closed
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ry @fictorial