Closed
Bug 581532
Opened 14 years ago
Closed 14 years ago
when remote tabs = true, Web pageloads are slow and broken
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: tchung, Unassigned)
References
Details
Attachments
(3 files)
When browser.tabs.remote=true is set, CNN.com takes about 45 seconds to load, and then it loads with broken layout everywhere. When set to false, page loads in about 3-5 secs, and renders as expected
See screenshots
Repro:
1) install 20100723, 9:14am nightly on n900
2) set browser.tabs.remote=false and load cnn.com. verify screenshot 1
3) now set browser.tabs.remote=true and load cnn. Verify screenshot 2. also notice the load time is much slower.
Expected:
- remote=false should still load page and layout as step 2 does
Reporter | ||
Comment 1•14 years ago
|
||
Reporter | ||
Comment 2•14 years ago
|
||
browser.tabs.remote=true is a pretty bad user experience. nom to block.
tracking-fennec: --- → ?
Tony, just to be clear, (3) refers to loading cnn.com before any other web content with remote=true?
If so, I suspect bug 582032 will help quite a bit.
Reporter | ||
Comment 6•14 years ago
|
||
Thats right Chris. In fact, no other web content was loaded after flipping to true; except cnn.com.
Comment 7•14 years ago
|
||
is this better now?
Reporter | ||
Comment 8•14 years ago
|
||
its a tad bit better in performance and page rendering, but its still not what i would expect as a normal user.
I dont know how better than to explain that the page is trying to redraw sections of the page in blocks, and it doesnt always line up the images. i can see if there's a way to capture what i see on video somehow.
Reporter | ||
Comment 9•14 years ago
|
||
Another screenshot showing the content body never loaded
Reporter | ||
Comment 10•14 years ago
|
||
qa update here. With the 20100812 trunk nightly, pages are redrawing properly now. Unfortunately, the page load time is still incredibly slow.
My tests: (loading www.cnn.com and recording start-to-stop times (watching the throbber switch to a favicon)
1. 1:04.5
2. 0.58.3
3. 0.58.8
4. 0.48.4
5. 0.45.6
Should we track the perf issue of page load in a seperate bug?
Updated•14 years ago
|
Comment 11•14 years ago
|
||
tchung - do you think we should close this and track the slow part of this bug in bug 588050?
Reporter | ||
Comment 12•14 years ago
|
||
Doug, yep agree. someone please mark this bug as resolved fixed by bug 582032, and we can continue this in the other perf bug.
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 13•14 years ago
|
||
Verified fixed on Mozilla/5.0 (X11; U; Linux armv7l; en-US; rv:2.0b4pre) Gecko/20100818 Namoroka/4.04pre Fennec/2.0a1pre. Pageloads are displayed correctly.
Status: RESOLVED → VERIFIED
Assignee | ||
Updated•11 years ago
|
tracking-fennec: ? → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•