Skip to content
This repository has been archived by the owner on Jun 19, 2020. It is now read-only.

casperjs can't be killed and wastes memory #96

Merged
merged 1 commit into from
Apr 28, 2012
Merged

Conversation

jart
Copy link
Contributor

@jart jart commented Apr 27, 2012

This patch fixes a bug where casperjs' python launcher process won't pass along kill signals to the phantomjs subprocess. This patch works by using an exec system call which causes the phantomjs subprocess to completely replace the casperjs parent process (while maintaining the same pid). This patch also has the added benefit of saving 10 megs or so of memory because the python process is discarded.

Thank you in advance for merging this and I hope you'll forgive me for the hyperbolic title :]

This fixes a bug where casperjs' python launcher process won't pass along kill
signals to the phantomjs subprocess. This patch works by using an exec system
call which causes the phantomjs subprocess to completely replace the casperjs
parent process (while maintaining the same pid). This patch also has the added
benefit of saving 10 megs or so of memory.
@n1k0 n1k0 merged commit ca07f6e into casperjs:master Apr 28, 2012
@n1k0
Copy link
Member

n1k0 commented Apr 28, 2012

Yay, pretty cool enhancement, thanks for contributing :)

@jart
Copy link
Contributor Author

jart commented Apr 28, 2012

Thank you for making this lovely project

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

Successfully merging this pull request may close these issues.

2 participants