-
Notifications
You must be signed in to change notification settings - Fork 302
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Memwatch failed to build with node v0.11.16 #59
Comments
Similar output for the just released node 0.12.0. Is this project still being worked on? |
If project is dead, do you know any project able to replace memwatch ? |
This can be fixed by fixing some variables in the source but 2013 was the last commit and thats a long time ago so I doubt this will still be officially updated. But there are a lot of new similar modules, one is found here. |
Thanks. But this project does not totally replace memwatch. The good thing with memwatch is the detection of memory leak in realtime. In dev mode, when my app is running, memwatch often check the heap and inform me if it grows 5 consecutive times after GC. Heapdump module seems to just offer snapshot and inspection. No background task for realtime control. Do you now a module doing that (in the "lot of similar modules"). I don't find this. Thanks. |
At this point, I'm just moving away from this sort of monitoring. I can detect memory leaks by watching process memory usage from the system. And then I can debug using heapdump and node-inspector. |
Ok thanks. I'm sad... |
@majimboo is there a documentation about what to fix? I try to install BipIO on my mac. This fails, cause memwatch won't be installed... |
@saschakiefer , @jeremieca , @panta82 someone already fixed it. I guess its on the pull requests. https://github.com/marcominetti/node-memwatch |
pull request here #60 |
Hello,
All the problem is describe in title !
Thanks !
The text was updated successfully, but these errors were encountered: