485277 - Weave slows down opening of new windows

Status: RESOLVED FIXED

(Cloud Services :: General, defect, P1)

Description

[Jürgen Kreileder]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b4pre) Gecko/20090325 Firefox/3.5b4
Build Identifier: 0.2.117

When Weave is enabled, new windows (either opened manually or as a popup) open noticeably slower.

On a 2.8GHz MacBook Pro with Shiretoko as of today and javascript.options.jit.chrome=true:

* no add-on vs. weave as the only add-on: almost instantly vs. about 2 seconds
* many add-ons vs. many add-ons + weave: 1 second vs. about 4 seconds

In either case the delay until the new window shows is too long.

Reproducible: Always

Steps to Reproduce:
1. Start Firefox with Weave enabled
2. Open new window and stop the time until it shows
3. Repeat 1 and 2 with Weave disabled
Actual Results:  
When Weave is enabled, windows open slowly.  Even if Weave isn't configured to actually sync anything.

Expected Results:  
New windows show open only marginally slower than with Weave disabled.

Tested on OS X but I suspect it effects all platforms.

Comment 2

[Joe Drew (not getting mail)]

Shaver and I both see this. -> NEW

Comment 3

[piergallini]

Same here:

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b3)
Gecko/20090305
Firefox/3.1b3

Comment 4

[Ed Lee :Mardak]

Bug 486810's patch seems to fix this for me or at least speeds it up.

Fun with prototype getters inherited with __proto__ ;)

Comment 5

[Andrew Conkling]

This is not very noticeable for me anymore, even though one of my systems is rather slow. Does anyone notice this in 0.30+?

Comment 6

[Dan Mills [:thunder]]

The fix for bug 486810 should definitely make this better.  I'm going to close as FIXED, Ed please reopen if you had some specific additional fix in mind for this bug.

Comment 7

[Ed Lee :Mardak]

Dan, you mentioned getting rid of the 2-way mapping of history id/guid a while back. Did you want to file a bug on that?

Comment 8

[Dan Mills [:thunder]]

I thought we could use bug 481327 for that.