Closed Bug 602956 Opened 14 years ago Closed 14 years ago

UI lag when Sync in progress

Categories

(Firefox for Android Graveyard :: General, defect)

Product:
Firefox for Android Graveyard
Component:
General
Platform:
ARM
Android
Type:
defect
Priority:
Not set
Severity:
major

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: Nukeador, Assigned: crowderbt)

Details

The UI response time is OK until sync update is in progress, then the UI response time has more than 4 seconds delay (sometimes more than 7 sec) turning Firefox app unusable.

I'm testing Firefox 4.0b1 under Android 2.2 using a Nexus One phone.
I have to add that once the sync update process starts, it keeps "in progress..." forever (I can see that from prefs panel under sync group).
After some tests:

The UI lag is still present even if you click disconnect from sync.

Since I'm unable to kill firefox process, I had to reboot the phone, then the UI problem is not present if you don't connect to sync.
I have several messages in the error console, but there is no way to copy/paste them with their trace info:

Engine.Bookmarks WARN Error (NS_ERROR_MALFORMED_URI)
Engine.Bookmarks WARN Error procesing record: this._lazyMap is not a function

(it repeats docens of times)

Engine.Bookmarks WARN Error procesing record: meta is null
Assignee: nobody → crowderbt
bug 599928 might help. It helped for initial login.
The responsiveness issue at the core of this bug is largely mitigated by bug 570619, as far as I can tell.  The warning/error messages from your error console logs are interesting...  a couple of them need more investigation, at least one is the subject of another bug.
The meat of this is fixed by the landing of threaded-crypto on m-c.  I believe the logging mayhem is addressed elsewhere as well (if someone wants to be a friend of bugzilla and hunt down the pre-existing bugs for these log messages, that'd be great).
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
(In reply to comment #6)
> I believe the logging mayhem is addressed elsewhere as well (if someone wants
> to be a friend of bugzilla and hunt down the pre-existing bugs for these log
> messages, that'd be great).

All logging was disabled by default as per bug 599928. Flip the log.appender.debugLog.enabled pref to enable it again.
I believe we also have other bugs on a) silencing one of these warnings which is bogus and b) addressing or investigating the other...  just turning off logging isn't quite what I'm referring to....
The warnings in comment 3 are very weird, but I'm not sure they're bogus and that we have bugs on them. More context (the whole sync log) would be great here.
VERIFIED FIXED on:

Build ID: Mozilla /5.0 (Android;Linux armv7l;rv:7.0a1) Gecko/20110609 Firefox/7.0a1 Fennec/7.0a1 

Build ID: Mozilla /5.0 (Android;Linux armv7l;rv:6.0a2) Gecko/20110608 Firefox/6.0a2 Fennec/6.0a2

Device: HTC Desire Z (Android 2.2)
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.