18800 - Collapsing sidebar during page load causes browser to crash

Status: VERIFIED WORKSFORME

(SeaMonkey :: Sidebar, defect, P1)

Description

[Igor]

Overview Description:  Minimizing or closing the "My Panels" customizable panel
on the left-hand side of the browser window while the page is loading causes the
browser to crash.

Steps to Reproduce:
1) Type one of the above URLs into the Location box.
2) Hit return.
3) While the page is loading and rendering in the browser window, click on the
light blue colored vertical bar embedded in the dark blue vertical seperator at
the left-hand side of the browser window.

Actual results:  The browser crashes.

Expected Results:  The bar should shift left closing (minimizing) the "My
Panels" Frame.  The rendering page should appropriately shift left.

Build Date:  11/13/1999, Linux Redhat 6.1 kernel 2.2.12-20

Additional Information:
For some reason the browser does not fail on all pages when they are loading.
For example www.mozilla.org does not cause the browser to crash when the Frame
is collapsed while the page is loading.  However--I don't know if this is
related or a seperate bug--collapsing and opening the frame multiple times while
the page is loading ultimately causes the browser window to turn black with the
result that no content is then visible.  If this is a seperate bug, please let
me know and I'll write it up.

Comment 1

[leger]

Setting component.

Comment 2

[Steve Lamm]

This was fixed last week. Paul is looking up the duplicate bug number for me.

Comment 3

[Steve Lamm]

Whoops, I mistook this bug for another one. I ran today's verification build and
the sportsline page does have problems.

Comment 4

[Steve Lamm]

I got the browser to hang twice, but now it works ok.

Comment 5

[don]

So is this really reproducible enough to try fixing?

Comment 6

[Steve Lamm]

I have not been able to reproduce this since this morning.
Resummarizing.

Comment 7

[Steve Lamm]

I cannot reproduce this crash. Marking worksforme.

Comment 8

[Paul MacQuiddy]

I'm going to mark verified, though I don't doubt that this bug may still lurk
out there. However, I think it's probably related to bug 17572