Bug 171258 - Firefox hangs briefly the first time a dialog is opened
Summary: Firefox hangs briefly the first time a dialog is opened
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: rawhide
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Christopher Aillon
QA Contact:
: 173150 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2005-10-20 00:01 UTC by Patrick Barnes
Modified: 2007-11-30 22:11 UTC (History)
6 users (show)

Clone Of:
Last Closed: 2005-12-17 19:28:34 UTC

Attachments (Terms of Use)

Description Patrick Barnes 2005-10-20 00:01:57 UTC
Description of problem:
Firefox in Rawhide hangs for several seconds the first time a dialog is opened.
 For me, it seems to hang for 5-10 seconds, but I've heard others say it hangs
up to 15 seconds.  After the first dialog, there are no further delays.

Version-Release number of selected component (if applicable):
Last tested: firefox-1.5-0.5.0.beta2
Appears to have affected all Rawhide versions of Firefox for about the last week

How reproducible:

Steps to Reproduce:
1. Close Firefox (if running)
2. Open a new instance
3. Visit a site that causes a dialog to appear
 * Password dialogs (HTTP Basic auth or Master Password) seem to be the best
Actual results:
Firefox hangs for several seconds before accepting input.

Expected results:
The dialog should appear and immediately accept input.

Comment 1 Zuirdj 2005-11-04 03:49:20 UTC

Also when I select "save link as", the download dialog hangs depending on the
number of tabs opened or the size of them.

Comment 2 Patrick Barnes 2005-11-04 06:16:07 UTC
That sounds like a different issue, and one that I am not seeing.  If this is a
problem you are continuing to see, and you can be more specific, you may need to
file a separate bug report.  You might want to see if anyone else is having the
same problem first.  I am not seeing it and have not heard any similar complaints.

Comment 3 Patrick Barnes 2005-11-04 06:17:33 UTC
After reloading my system with a fresh devel install, the delay before the
dialogs are ready to accept input has decreased, but is still longer than it
should be.  I'd like to know if anyone can verify that this problem continues to
manifest itself.  I know I've heard other complaints, but not recently.

Comment 4 Thomas M Steenholdt 2005-11-04 12:47:55 UTC
I have the same problem where the first dialog makes firefox unresponsive for at
~10-15 seconds. SSL domain mismatch, javascript popups, whatever pops up first
will cause firefox-bin to consume NEAR 100% CPU and become unresponsive for this
amount of time...

I just tried the same with a self-built version of RC1 under FC4 and it's
exactly the same problem.

Comment 5 Thomas M Steenholdt 2005-11-04 13:06:24 UTC
The binary linux distribution of 1.5rc1 (compat-libstdc++ based) from
mozilla.org does NOT exhibit this behaviour.

Comment 6 Thomas J. Baker 2005-11-05 13:43:25 UTC
firefox-1.5-0.5.0.rc1 just added to rawhide still exhibits this problem for me.

Comment 7 Thomas M Steenholdt 2005-11-15 22:58:32 UTC
Just rebuilt rc2 on my FC4 which had this problem on rc1 and it appears that the
bug is gone... Can't wait to hear what kind of result you guys have.

Comment 8 Marius Andreiana 2005-11-16 19:03:29 UTC
*** Bug 173150 has been marked as a duplicate of this bug. ***

Comment 9 Thomas M Steenholdt 2005-11-17 10:12:39 UTC
strange.. problem has reappeared on my system and i can't think of why...
I'll try to figure out what's happening!

Comment 10 Lars G 2005-11-21 12:45:00 UTC
-rc3 stalls here too.

Comment 11 Thomas M Steenholdt 2005-12-06 23:14:44 UTC
firefox-bug305970.patch from the rawhide firefox-1.5-1 package resolves the issue.

Comment 12 Zuirdj 2005-12-13 14:13:22 UTC
firefox-1.5-1.1 works OK for me. 

Comment 13 Patrick Barnes 2005-12-13 14:25:34 UTC
Seems to be working fine here, too.

Any additional comments or observations before I close this bug?

Comment 14 Patrick Barnes 2005-12-17 19:28:34 UTC
I'm closing this bug as RAWHIDE.  Thanks, everyone, for your attention to this.

Note You need to log in before you can comment on or make changes to this bug.