1384095 - Intermittent browser/base/content/test/urlbar/browser_urlbarUpdateForDomainCompletion.js | application crashed [@ mozilla::net::nsSocketTransport::InitiateSocket()]

Status: RESOLVED WORKSFORME

(Core :: Networking, defect, P5)

Description

[Treeherder Bug Filer]

Filed by: cbook [at] mozilla.com

https://treeherder.mozilla.org/logviewer.html#?job_id=116162391&repo=mozilla-central

https://queue.taskcluster.net/v1/task/W53up_USQ5ivpeGtYr1pVw/runs/0/artifacts/public/logs/live_backing.log

Comment 1

[Kershaw Chang [:kershaw]]

This is really weird...

Could this have something to do with TFO?

Comment 2

[Dragana Damjanovic [:dragana]]

(In reply to Kershaw Chang [:kershaw] from comment #1)
> This is really weird...
> 
> Could this have something to do with TFO?

I do not think this is TFO.

The test fails because we are trying to access non-local address. It is failing so rarely that it is going to be hard to get a log. I have seen 2 failure, one on 20th and one on 21st.

We can hait for some more stats on this error.

Comment 3

[Shih-Chiang Chien [:schien] (UTC+8) (use ni? plz)]

I did nslookup for the reported non-local address. It points to a ec2 machine under us-west-2.compute.amazonaws.com. Double check our code base and I didn't find any obvious code that will access this domain.

Comment 4

[u408661]

This looks like it could be related to bug 1348275 - Evelyn, could you take a look?

Comment 5

[Evelyn Hung]

We have turned off speculative connect by default in test environment(network.http.speculative-parallel-limit is 0)[1], and this test case doesn't turn it on. 

I guess the ec2 machine is our testing server. If so, there are two possibilities of this failure:

(1) the code landed in bug 1348275 was triggered and the necko created a dummy channel object in test environment before checking the pref. Would it possible that the dummy channel object went wrong and wasn't destroyed?

(2) the test did caught a failure because of some unknown reasons that we didn't complete "example" to "www.example.com" when the enter key is hit and docshell is trying to load it. As I know, this url-complete handling is different from the autocomplete of location bar, and it's handled along the line of URI loading.

[1] http://searchfox.org/mozilla-central/rev/bd39b6170f04afeefc751a23bb04e18bbd10352b/testing/profiles/prefs_general.js#44
[2] http://searchfox.org/mozilla-central/rev/b52285fffc13f36eca6b47de735d4e4403b3859e/netwerk/base/nsIOService.cpp#1866-1898

Comment 6

[Honza Bambas (:mayhemer)]

Has this ever happened again?  Looks like we can close this now.  Please feel free to reopen.