Closed
      
        Bug 504057
      
      
        Opened 16 years ago
          Closed 16 years ago
      
        
    
  
Slow loading of relatively large pages
Categories
(Firefox :: General, defect)
Tracking
()
        RESOLVED
        DUPLICATE
          of bug 477564
        
    
  
People
(Reporter: thomas_weiss, Unassigned)
Details
Attachments
(1 file)
| 4.29 KB,
          application/x-gzip         | Details | 
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1) Gecko/20090624 Firefox/3.5
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1) Gecko/20090624 Firefox/3.5
I noticed a performance problem with a page containing a custom select box composed of normal div and input tags. On my system (Intel Pentium D 2.8GHz) with a select box of around 400 entries Firefox loads the page and after about 3 seconds it consumes 100% CPU time for about 10 seconds. The more entries the select box has the longer it takes to render the page.
The problem does not exist in Firefox 3.0 (rendering there is much faster). I also tested with the current nightly build (firefox-3.5.1pre.en-US.linux-i686.tar.bz2, 2009-07-13). There the problem remains.
Reproducible: Always
Steps to Reproduce:
1. Build a page containing something like this:
<div>
	<div>
		<input type="checkbox">
		<span>Test</span>
		<input value="Test" type="hidden">
	</div>
</div>
2. Duplicate the inner div a few hundred times.
3. Load the resulting page.
Actual Results:  
Firefox consumes 100% CPU time for a few seconds while rendering the page.
Expected Results:  
Rendering should happen very much faster.
The problem also exists with Firefox on Windows and Mac.
|   | Reporter | |
| Comment 1•16 years ago
           | ||
|   | Reporter | |
| Updated•16 years ago
           | 
Version: unspecified → 3.5 Branch
|   | ||
| Comment 2•16 years ago
           | ||
Changing browser.sessionstore.privacy_level improves situation.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
          You need to log in
          before you can comment on or make changes to this bug.
        
Description
•