Closed
Bug 316247
Opened 20 years ago
Closed 20 years ago
Once per session, Firefox will hang CPU intensive for up to 1 minute
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 305970
People
(Reporter: ilya.konstantinov+future, Unassigned)
Details
(Keywords: hang)
Attachments
(1 file)
|
4.97 KB,
text/plain
|
Details |
This CPU-intensive (although finite; it can take anywhere from 3 seconds to 1 minute) operation usually happens when:
1. starting a drag operation
2. emiting an JS alert or a File Save dialog box
|
Reporter | |
Comment 1•20 years ago
|
||
When breaking into the "hung" Firefox with a debugger, the CPU intensive operation appears to have something to do with the widget/gtk -> pango -> fontconfig. I'm not running a debug build so that's all I've gathered. I'll try to gather some more info soon by running a debug build of pango and fontconfig.
From the nature of the bug (once per session), I can guess some sort of font-related precalculation is taking place here.
|
||
Comment 2•20 years ago
|
||
Do all views redisplay and scroll to top, so the duration of the hang depends on the number × complexity of documents? This sounds like bug 305970.
|
|
Reporter | |
Comment 3•20 years ago
|
||
Tuukka, thanks for the match. Bug 305970 indeed describes what I'm seeing the best, though its summary could've been made more precise.
*** This bug has been marked as a duplicate of 305970 ***
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•