423170 - Seamonkey takes 43 seconds to open new browser window

Status: RESOLVED WORKSFORME

(SeaMonkey :: General, defect)

Description

[Igor Velkov]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b5pre) Gecko/2008031501 SeaMonkey/2.0a1pre
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b5pre) Gecko/2008031501 SeaMonkey/2.0a1pre

Seamonkey takes 43 seconds to open new browser window.
It doesn'n matter, want I open link from web page in new window, link in mail, or open new browser in menu. It takes 42-43 seconds.
I have a lot of extensions, but effect still present with "safe mode".

Reproducible: Always

Comment 1

[Matthias Versen [:Matti]]

Did you try to create an additional test profile ?
wfm with a current sm nightly on win32

Comment 2

[Igor Velkov]

New profile does not have this problem.
So, problem inside my profile. But how it can be, if no extension is running in safe mode?

Comment 3

[Matthias Versen [:Matti]]

It's possible thaz the safemode doesn'T deactivate everything or some other setting in your profile caused this.

Comment 4

[Igor Velkov]

I catch it!
The guilty was user_pref("browser.chrome.load_toolbar_icons", 2);
if value is 1 or 0 - all work fine;
What's changed, if I see this effect about 1 week, at home and at work, and have value "2" around a year?

So, I don't know, is this bug, or not.

Comment 5

[Frank Wein [:mcsmurf]]

I guess it's waiting for all the site icons to load via HTTP. Need to look at the check-ins to see if something changed there.

Comment 6

[Frank Wein [:mcsmurf]]

Igor: Do you know with which build this behavior changed? If you have some time (and possibly a somewhat fast connection), it would be cool if you can test this. Go to http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/ and download some builds around that time (you said one week ago, so test around 2008-03-07). Normally the folders with -02 in the name should have the Windows builds in it, you can just download the .zip builds and extract them for faster testing.

Comment 7

[Igor Velkov]

Trying to find first broken build I found this problem not affects any more any release.

Before creating this bug I see it on 3 different pc at 2 different places - at home and at work.

Look like it was internet (network) problem. Possible DNS.
Now this bug unreproduceable.

Sorry for trouble.

Possible, bug can be closed as invalid.

Comment 8

[Frank Wein [:mcsmurf]]

Ok, closing as wfm.