Skip to content
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

Kill phantom process #34

Open
JacksonGariety opened this issue Jun 6, 2016 · 2 comments
Open

Kill phantom process #34

JacksonGariety opened this issue Jun 6, 2016 · 2 comments

Comments

@JacksonGariety
Copy link
Contributor

Phatom itself doesn't seem to leak memory for me, however, when I close the screenshot stream, it seems like about ~40mb of data get left behind resulting in a serious memory leak.

I'm assuming that phantom is leaving something hanging around on its end, or not exiting?

It happens every time the node server throws Error: ECONNRESET.

@JacksonGariety
Copy link
Contributor Author

JacksonGariety commented Jun 6, 2016

I only write this as an issue here since I've attached an on('error') to every stream in my server, yet memory continues to leak. Perhaps a stream is getting left behind in index.js?

This one, maybe: https://github.com/kevva/screenshot-stream/blob/master/index.js#L56

@sindresorhus
Copy link
Contributor

Not much we can do based on this information, but you could probably use node --inspect in latest Node.js version to inspect memory usage using DevTools and see where it's coming from.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants