620192 - Slow Script Warning Dialog on resource://services-sync/base_records/wbo.js:101

Status: RESOLVED DUPLICATE of bug 561452

(Firefox :: Sync, defect)

Description

[(mostly gone) XtC4UaLL [:xtc4uall]]

Build: Mozilla/5.0 (Windows NT 5.1; rv:2.0b9pre) Gecko/20101218 Firefox/4.0b9pre ID:20101218030347 (http://hg.mozilla.org/mozilla-central/rev/4f03895d544b).

I set up a new Profile and copied over my places.sqlite file from my "Daily Use Profile" for Syncing the Bookmarks & History Data with my old Weave/Sync Account (overwriting all already saved Server Data).

Got the Stop/Continue Unresponsive Script Warning Thingy for resource://services-sync/base_records/wbo.js:101

See http://mxr.mozilla.org/mozilla-central/source/services/sync/modules/base_records/wbo.js#101

Comment 1

[Richard Newman [:rnewman]]

Removing incorrect blocking annotation.

Comment 2

[(mostly gone) XtC4UaLL [:xtc4uall]]

Forgot to note that i got a second Slow Script Warning for resource://services-sync/util.js:573 in the same Sync Process. I was about to file it separately but put it here now.

http://mxr.mozilla.org/mozilla-central/source/services/sync/modules/util.js#573

Sorry for the wrong Bug Blaming - I relied on the HG Log.

Comment 3

[Richard Newman [:rnewman]]

(In reply to comment #2)
> Forgot to note that i got a second Slow Script Warning for
> resource://services-sync/util.js:573 in the same Sync Process. I was about to
> file it separately but put it here now.

Could be anything, really. If you're getting those in several places it's unlikely to be a useful pointer to a problem. If you're consistently (across multiple syncs and multiple restarts of the browser) getting warnings in the same places, then that's a different story.


> Sorry for the wrong Bug Blaming - I relied on the HG Log.

Yeah, the work for that bug touched about 4,000 lines of code, so it kinda screws up blame :)

Just for future reference, "depends on" and "blocks" are typically used for tracking work dependencies, not for suggesting a possible cause for the bug. The best way to do that is just to mention the bug by name: e.g., Bug 603489. (That number is etched into my memory!)

Comment 4

[Philipp von Weitershausen [:philikon]]

This has been reported a few times. I believe Sync.js is the culprit, but that's just a hunch.