How to close a browser on a selenium RC server which lost it's client
问题 suppose a client starts a selenium session on an RC server, but at the middle of the session the client "went away". The browser will remain open, and eventually, after enough such dropped sessions, there will be enough "orphan" browsers to slow down the computer. How can I make sure those browsers are closed? Why isn't there a "keep-alive" part in the protocol to make sure the client is still responsive and if not kill the session? 回答1: Any browser instance has a session_id you can store.