609396 - Some Frames are rendered inconsistently after restart.

Status: RESOLVED FIXED

(Core :: DOM: Navigation, defect)

Description

[Stefan]

User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:2.0b8pre) Gecko/20100101 Firefox/4.0b8pre
Build Identifier: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b8pre) Gecko/20100101 Firefox/4.0b8pre

After a restart certain nested framesets are not properly rendered.

Reproducible: Always

Steps to Reproduce:
1. Start FF with no profile.
2. Close all but last tab, 
4. Load in the first (and only tab) the testcase URL.
5. open two (2) additional tabs and load in them the testcase URL.
6. close FF. Press "Save and Quit"
7. start FF.
Actual Results:  
The second and the third tab each show a blank right frame.
Only the first tab contains the properly rendered content.

Expected Results:  
Every tab's content is properly rendered.

1. hg bisect gave:

The first bad revision is:
changeset: 51138:cbf6e0a17783
user: Olli Pettay <[e-mail]>
date: Sat Aug 21 00:26:52 2010 +0300
summary: Bug 588643 - Crash in [@ nsDocShell::SetHistoryEntry ], r=bent/neil, a=blocking

If you disable mChildren.SetCount(aOffset); in nsSHEntry.cpp the error vanished. Unfortunately there is no testcase in Bug 588643.

2. If you (idependently from 1.) set both browser.cache.disk.enable and browser.cache.memory.enable to false the error vanished, too.

Comment 1

[Stefan]

While the given URL seems to give strictly reproducible result here is another URL which does sometimes not: http://www.apacam.org/testdisc_frm.htm (You may have to open more frames).

I could not

Comment 2

[Stefan]

yet prepare an "isolated" testcase.

Comment 3

[Stefan]

another URL: http://www.awstats.org/
none of the three pages renders correctly after restart.

Comment 4

[Mike Beltzner [:beltzner, not reading bugmail]]

--> Core::Document Navigation

(Stefan, thanks for the detailed bug report and regression range; next time, please file regression bugs in the same component as the bug which caused the regression)

Comment 5

[Stefan]

Fixed with fix of Bug 632835
(http://hg.mozilla.org/mozilla-central/rev/6229fab0d2e6)