Closed
Bug 1124356
Opened 11 years ago
Closed 11 years ago
Exceptional request slowdown after FF has been open for a while
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: bjornson, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.95 Safari/537.36
Steps to reproduce:
Leave FF open for several hours (probably 4+). Test speed (e.g. speedof.me).
Actual results:
Download drops to 50 kbps, upload 80 kbps. Same test in Chrome, FF35 or a freshly restarted FF38 gives 60 Mbps down and 113 Mbps up.
I'm happy to attach any dump files or log files, but I'm not sure what will be relevant -- please advise. This has been happening to the last ~week of nightly builds.
Comment 2•11 years ago
|
||
Can you reproduce the same behaviour if you turn off e10s in the prefs?
Flags: needinfo?(bjornson)
This seems to have gone away in the last nightly build.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Flags: needinfo?(bjornson)
Resolution: --- → INVALID
Comment 4•11 years ago
|
||
Mistakenly filed against Firefox 38 and should be instead 38 Branch. Sorry for the spam. dkl
Version: Firefox 38 → 38 Branch
Comment 5•10 years ago
|
||
Commits pushed to master at https://github.com/mdn/browsercompat
https://github.com/mdn/browsercompat/commit/646b9541206eab5fc1420106942c7d15b079e5b6
fix bug 1124356 - Improve UI for async commit
When the server is in async mode, change text after a successful sync,
and start polling the server to reload with new data IDs.
Also, only set the handler for the commit button during page setup.
https://github.com/mdn/browsercompat/commit/16b0dc570590146867f1c5ea35298b81102e5cf6
Merge pull request #87 from mdn/async_commit_1224356
fix bug 1124356 - Improve UI for async commit
Updated•10 years ago
|
Resolution: INVALID → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•