1378041 - chrome://marionette/content/server.js, line 350: Component returned failure code: 0x804b0036 > (NS_ERROR_SOCKET_ADDRESS_IN_USE) [nsIServerSocket.initSpecialConnection]

Status: RESOLVED FIXED

(Remote Protocol :: Marionette, enhancement)

Description

[Henrik Skupin [:whimboo][⌚️UTC+1]]

(In reply to Henrik Skupin (:whimboo) from bug 1362293 comment #13)
> In the case of an ASAN build I see the following output of Marionette in the
> log:
> 
> https://treeherder.mozilla.org/logviewer.
> html#?repo=autoland&job_id=111383412&lineNumber=1204
> 
> [task 2017-07-01T21:34:32.594790Z] 21:34:32     INFO -  1498944872582
> Marionette	INFO	Listening on port 2828
> [task 2017-07-01T21:34:32.692007Z] 21:34:32     INFO -  JavaScript error:
> chrome://marionette/content/server.js, line 350:
> NS_ERROR_SOCKET_ADDRESS_IN_USE: Component returned failure code: 0x804b0036
> (NS_ERROR_SOCKET_ADDRESS_IN_USE) [nsIServerSocket.initSpecialConnection]
> 
> This is strange because the `listening` output line should only be visible
> when the server got correctly started, and then even afterward. I wonder if
> there is a situation when we try to create the server twice. I will file a
> Marionette bug for that.

As it looks like by bug 1254136 I have also seen this in the past for Firefox UI tests when running with --js-debugger.

Comment 1

[Henrik Skupin [:whimboo][⌚️UTC+1]]

I can't see this anytime longer since my patch on bug 1254136 landed.