Closed
Bug 568028
Opened 15 years ago
Closed 14 years ago
Enhancement: Make sure weave uses a separate thread
Categories
(Firefox :: Sync, defect)
Firefox
Sync
Tracking
()
RESOLVED
WONTFIX
Future
People
(Reporter: ashah, Unassigned)
Details
Build ID for Fennec:
Mozilla/5.0(X11;U;Linux armv7l;en-US;rv1.9.2.5pre)Gecko/20100524Namoroka/3.6.5 pre Fennec/1.1b2pre
I opened 6 to 7 tabs with heavy sites like youtube, CNET, Yahoo, CNN, Amazon.
Then I tried to login to my weave profile.
Behavior:
For weave 1.3b7, it froze the browser twice.I had to restart the phone. Then i shifted back to weave 1.2.3 and ran the same test case. This time it didnt freeze but the performance was very very slow. The data in the fields(username, password, phrase) was being typed slow.
Note that this behavior happens when the pages are still loading. Once the pages were loaded completely, everything is back to normal.
Updated•15 years ago
|
Component: Fennec UI → Sync
OS: Linux (embedded) → All
QA Contact: fennec → sync
Hardware: ARM → All
Target Milestone: --- → Future
Comment 1•14 years ago
|
||
I think my "problem" may be related:
when moving a bookmark in the bookmark pane on the left, weave sync immediately starts to push the change upstream. While that push action is active, scrolling in the bookmark pane is some sort of unresponsive, ie. the content doesn't immediately refelect when dragging the vertical scrollbar or the scrollbar doesn't reflect scrolling using the mouse wheel.
Change from "enhancement" to "bug"?
Comment 2•14 years ago
|
||
Original report is just old Fennec plus blocking UI operations on 2010-era phones. XUL Fennec, so I'm going to close this.
Anonymous recent commenter: yes, some parts of Sync block the main thread and make the UI unresponsive. Please feel free to file a new bug, rather than adding to this one.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
| Assignee | ||
Updated•7 years ago
|
Component: Firefox Sync: Backend → Sync
Product: Cloud Services → Firefox
You need to log in
before you can comment on or make changes to this bug.
Description
•