Closed
Bug 455017
Opened 17 years ago
Closed 7 years ago
entire user interface freezes while loading completions for first URL typed on cold start
Categories
(Firefox :: Address Bar, defect)
Tracking
()
RESOLVED
INACTIVE
People
(Reporter: zwol, Unassigned)
Details
(Whiteboard: [DUPEME][Tsnappiness])
Attachments
(1 file)
|
505.76 KB,
application/x-bzip
|
Details |
On cold start - that is, with a just-started browser process and none of the profile data in the OS's memory cache - the entire UI freezes up for (what feels like) entire seconds immediately after I type one character in the URL bar, and then again shortly before the first page load completes. Similar but shorter hangups happen on typing into the URL bar in new tabs, until (I am guessing) the entire history database has been read into memory, at which point they stop.
I am using an XFS partition for everything, so I doubt this is due to the infamous fsync problem.
I attach the output of strace -ff -tt -p <browser-pid>, starting after the initial display was completely loaded (this is about:blank for me) and ending, um, when nspluginwrapper crashed and took the browser with it. In that window I opened three tabs and requested the load of two web pages: https://mail.google.com/mail/#inbox and http://zwol.livejournal.com/friends/ (in both cases, by typing the first two characters of the domain name and then selecting the first result from the completions list). I would have loaded another web page in the third tab if the browser hadn't crashed.
Probably a lot of the traces in the tarball are uninteresting, but I don't know which thread is which. I did find one thread that seemed to switch back and forth between lots of read/write/select on one fd and lots of lseek/read on another fd -- if one of those is communication with the X server and the other is a disk database, that would explain the UI hickups.
| Reporter | ||
Comment 1•17 years ago
|
||
| Reporter | ||
Comment 3•17 years ago
|
||
seems plausible that this would bite anyone anywhere, if the problem really is that the UI thread is tied up with the database I/O.
OS: Linux → All
Hardware: PC → All
Comment 4•17 years ago
|
||
This was already reported a few times so I guess this is a duplicate.
Whiteboard: [DUPEME]
Updated•16 years ago
|
Whiteboard: [DUPEME] → [DUPEME][Tsnappiness]
Comment 5•13 years ago
|
||
can someone still reproduce this?
| Reporter | ||
Comment 6•13 years ago
|
||
It doesn't happen for *me* anymore with current builds on similar hardware and OS.
Comment 7•7 years ago
|
||
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INACTIVE
You need to log in
before you can comment on or make changes to this bug.
Description
•