Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Calling #fork ends up closing webkit-server #192

Closed
jyurek opened this Issue Oct 13, 2011 · 2 comments

Comments

Projects
None yet
3 participants
Member

jyurek commented Oct 13, 2011

Calling #fork causes the at_exit hooks to be duplicated, which means webkit-server is shut down. This can be avoided by calling exit! in the fork block, but that requires developer involvement and knowledge. It would be good if we didn't have to do that.

Contributor

halogenandtoast commented Oct 14, 2011

Fixed with 3eb366e

tmaier commented Oct 14, 2011

I'm the guy of issue #181 "I still get WebkitNoResponseError".

Just to give you guys an update: I tried the most recent HEAD of revision b4faa3a
But I still get my errors Capybara::Driver::Webkit::WebkitNoResponseError: No response received from the server., followed by Errno::EPIPE: Broken pipe messages.
This means this fix did not solve my issue with capybara-webkit.

I'll update my original issue soon if there was any change in the :webkit_debug output.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment