Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
The following problems generally mean that
webkit_server has crashed:
QCoreApplication::postEvent: Unexpected null receiver
- All tests fail after a given test
WebkitInvalidResponseError with "Invalid command"
Errno::EADDRNOTAVAIL: Can't assign requested address
Please include a debug log and all versions in use when reporting a crash.
If you encounter one of these errors, please set your driver to debug mode and attach all output from your test to the issue. Without this output, we can't do much to fix your issue.
Capybara::Webkit.configure do |config| config.debug = true end
If you're using Qt 4, your crash may be fixed by updating to Qt 5. The latest 4.x release was several years ago, and many bugs have been fixed since then. Please update to Qt 5 before reporting any issues to the capybara-webkit team.
You can see which versions you're running by running the following in a Capybara session:
Please include the relevant versions when reporting a crash.
If you happen to be using a mac, your mac console may reveal interesting things if the problems that you are running into have caused thread crashes. You can access this on your mac within the /Applications/Utilities folder as the application "Console". Clear the console display and attempt to reproduce the problem. If your problem is causing threads to crash you should see a crash report within the "User Diagnostic Reports" section in the left hand nav bar after reproducing the problem.