1335241 - HTTP Redirects stop working after some time

Status: RESOLVED WONTFIX

(WebExtensions :: General, defect)

Description

[Thomas Daede [:TD-Linux]]

On nightly with e10s, usually after about a day of usage, the browser gets into a state where HTTP redirects stop working. For example, if I go to google.com, I will see a 302 redirect page to www.google.com, with the 302 redirect HTML, but no redirection will happen. This affects all open tabs at the same time and persists until a restart.

I can create a networking log, though when I attempted to do this it generated a huge 11MB log with a lot of data. Is there a way to filter that to only something useful?

I haven't verified if this is caused by e10s yet.

Comment 1

[Thomas Daede [:TD-Linux]]

One other trend: I seem to get a shutdownhang 100% of the time when restarting after this happens, but never otherwise. Unfortunately the shutdownhang traces are random and useless.

Comment 2

[Valentin Gosu [:valentin] (he/him)]

Seems to me like a thread hangs and prevents both network activity and shutdown. My money is on the DNS thread.
Do you think you could gather some logs when this happens?
https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/HTTP_logging

Comment 3

[Thomas Daede [:TD-Linux]]

Attachment: log.txt-main.19190

Comment 4

[Thomas Daede [:TD-Linux]]

Attachment: log.txt-child.20121

Comment 5

[Dragana Damjanovic [:dragana]]

It is not DNS, DNS works just fine.

You are trying to connect to http://google.com which redirects (301) to http://google.com !!! Interesting

The redirect fails, is vetoed, with 0x80570021 which is NS_ERROR_XPC_JAVASCRIPT_ERROR_WITH_DETAILS (I think i got the correct one, finding the corresponding error from a code is not easy :) )

2017-02-04 23:03:45.773612 UTC - [Main Thread]: D/nsHttp nsHttpChannel::OnRedirectVerifyCallback [this=7fd19e546000] result=80570021 stack=2 mWaitingForRedirectCallback=1

Is this the last part of the log? Can you tell me what happened. You try to connect to http://google.com and you get 301 response? After that you tried to shutdown and it hung? Do you have crash id?

Comment 6

[Honza Bambas (:mayhemer)]

Thomas, any addons like NoScript, Ghostery or alike?  Can you provide a complete list by copying content of about:support page?  Thanks.

Comment 7

[Thomas Daede [:TD-Linux]]

Yes, that's the complete log attached (stopped a few seconds after loading the page). I see the 301 or 302 redirect HTML displayed by the browser. This happens for *all* redirects, I just used google.com as an example.

Here is an example shutdownhang: https://crash-stats.mozilla.com/report/index/93475286-69f2-49ba-a297-a09f12170206

Here is a list of enabled extensions (no greasemonkey scripts affect domains in question):

Application Update Service Helper	1.0	true	[e-mail]
DownThemAll! *nightly*	3.1.1pre.20170206.00h01m18s	true	[e-mail]
FlyWeb	1.0.0	true	[e-mail]
Form Autofill	1.0	true	[e-mail]
Greasemonkey	3.9	true	{e4a8a97b-f2ed-450b-b12d-ee082ba24781}
Multi-process staged rollout	1.9	true	[e-mail]
Page Shot	5.2.201701261751	true	jid1-NeEaf3sAHdKHPA@jetpack
Pocket	1.0.5	true	[e-mail]
Presentation	1.0.0	true	[e-mail]
SHA-1 deprecation staged rollout	1.0	true	[e-mail]
Shield Recipe Client	1.0.0	true	[e-mail]
Test Pilot	0.9.4-dev-045fca1	true	@testpilot-addon
uBlock Origin	1.10.6	true	[e-mail]
Web Compat	1.0	true	[e-mail]
WebCompat Reporter	1.0.0	true	[e-mail]

I'll iteratively delete addons to see if any are the cause (just deleted Page Shot and Test Pilot now)

Comment 8

[Dragana Damjanovic [:dragana]]

Any news regarding addons?

Comment 9

[Thomas Daede [:TD-Linux]]

Yes, I believe the DownThemAll addon to be the culprit. It seems it's also known for causing shutdown hangs in linked bug, but I don't know if it's due to the same issue.

Comment 10

[Jorge Villalobos [:jorgev] (he/him)]

Mass-closing bugs that relate to legacy versions of add-ons or are otherwise no longer worth tracking. Please comment if you think this bug should be reopened.

Sorry for the bugspam. Made you look, though!