Issue with phantomjs left running about behaving

[ggozad]

There is a test in browser.feature that just starts phantomjs. After its completion there is no phantomjs running, so at least on my mac I cannot reproduce it. Would you be able to make a test-case that fails?

[kageurufu]

I had this same issue.

For me, the dangling process was actually NodeJS, as I had installed PhantomJS through npm, in which bin/phantomjs is actually a node script, and it wasn't cleanly exiting. My solution was to use a distro installed copy of phantomJS instead of Node's, as I could not find a way for selenium or splinter to tell phantomjs to close in a way that didn't leave that dangling process.

[ggozad]

I am guessing we can close this then? Seems to be a phantomjs on linux issue.

[kageurufu]

We should probably wait for @lampmantech to confirm his issue is the same as mine, and then close