Lower network.http.max-connections to 48 on windows until bug 692260 is resolved

RESOLVED FIXED

Status

()

Core
Networking: HTTP
RESOLVED FIXED
6 years ago
6 years ago

People

(Reporter: jduell, Unassigned)

Tracking

unspecified
All
Windows 7
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox8+ fixed, firefox9+ fixed)

Details

(Whiteboard: [qa-])

Forked bug 692260 just so we have a separate bug # to land this workaround for aurora/beta while we continue to work on a full fix.
(Reporter)

Comment 1

6 years ago
landed attachment 568328 [details] [diff] [review] from bug 692260 on aurora/beta.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
OS: Linux → Windows 7
Hardware: x86_64 → All
Resolution: --- → FIXED

Comment 2

6 years ago
---------------------------------[ Triage Comment ]---------------------------------

Marking this as tracking to make sure the stopgap sticks for aurora9 and beta 8 and of course works as desired (fixing bug 692260).This is a large support issue in Firefox 7 where it regressed.

Bug 683280 tracks the real fix on mozilla-central / Firefox 10.
status-firefox8: --- → fixed
status-firefox9: --- → fixed
tracking-firefox8: --- → +
tracking-firefox9: --- → +
Is there something QA can do to verify this fix?
Whiteboard: [qa?]
(Reporter)

Comment 4

6 years ago
We've had trouble reproducing it, but users who are affected can generally repro it quickly.  So you could try to contact users who are having the issue on SUMO and see if having them set the pref to 48 fixes it for them.  And/or just monitor the forums (or talk to the SUMO folks who monitor the forums) to see if this workaround seems to be working for everyone who encounters this issue.
Not specifically verifiable by QA based on comment 4. CCing Cww on this bug to see if SUMO can help.
Whiteboard: [qa?] → [qa-]
You need to log in before you can comment on or make changes to this bug.