Closed Bug 716780 Opened 13 years ago Closed 13 years ago

Awesomescreen is often non-responsive

Categories

(Firefox for Android Graveyard :: General, defect, P4)

12 Branch
ARM
Android

Tracking

(fennec11+)

RESOLVED WORKSFORME
Tracking Status
fennec 11+ ---

People

(Reporter: samth, Assigned: lucasr)

References

Details

(Keywords: perf)

The awesomescreen is often almost completely non-responsive for me. In particular, (a) scrolling is very slow and laggy, and even worse, (b) tapping links usually does nothing. Sometimes, after a few taps, it will suddenly start loading the relevant page. Sometimes, the entry will highlight in green, but not start loading. This happens for all of the History, Top Sites, and Bookmarks tabs, although switching between the tabs works. The behavior is the same for Nightly Fennec. This is with an HTC Sensation, running Android 2.3.1.
Severity: normal → major
Status: UNCONFIRMED → NEW
Ever confirmed: true
Version: Firefox 11 → Firefox 12
Sam, does this happen all the time or only when you've just just started Fennec?
Lucas, this continues to happen even after I've been using Fennec for a while.
After a XUL Firefox profile migration?
To the best of my knowledge, no data was ever migrated from my XUL Fennec install to the Native Fennec installs.
Sorry, I was wrong about that -- some information was migrated, in particular some settings created by addons.
Keywords: perf
Lucas, perhaps adding some logging would be helpful? (like bug 709078)
Assignee: nobody → lucasr.at.mozilla
tracking-fennec: --- → 11+
Priority: -- → P4
This bug appears to be basically gone with the landing of the non-system storage.
(In reply to Sam Tobin-Hochstadt [:samth] from comment #8) > This bug appears to be basically gone with the landing of the non-system > storage. Great. I'm closing this bug then. Feel free to re-open if notice any problem again.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.