Hanging at end of spec run about celerity HOT 6 CLOSED

You're probably hitting this. Make sure to call Browser#close and all should be good. Please close this issue if that is the case.

from celerity.

Yeah, looks like it.

I'm driving Celerity through Capybara (via Culerity), so Capybara is already doing this:

@_browser = ::Culerity::RemoteBrowserProxy.new self.class.server, {:browser => :firefox, :log_level => :off}
at_exit do
  @_browser.exit
end

If I add a @_browser.close in there prior to the @_browser.exit then the hanging disappears.

There are no comments on that HtmlUnit ticket that you linked. Do you think it's a bug in HtmlUnit (ie. this will be a temporary workaround)? Or something that all consumers of HtmlUnit/Celerity will need to end up doing?

Cheers,
Wincent

from celerity.

Opened a ticket over in Capybara tracker to include Jonas in the discussion:

http://github.com/jnicklas/capybara/issues/issue/99

from celerity.

Yes - definitely an HtmlUnit bug IMO. I can't see any rationale for having non-daemon Java threads hanging around.

They usually write to me before doing new releases, I'll make sure to bring it up then.

(Btw, there's no Celerity::Browser#exit, so I'm not sure what Culerity's doing there. I'm guessing that's where the close() call should go, i.e. not in Capybara).

from celerity.

Here is where Culerity's exit method is defined:

http://github.com/langalex/culerity/blob/master/lib/culerity/remote_object_proxy.rb

At a glance, can't say I really know what it does.

from celerity.

Closing this since the problem is not in Celerity.

from celerity.