Closed Bug 360616 Opened 18 years ago Closed 17 years ago

Crash [@ nsCSSFrameConstructor::WipeContainingBlock] on this site sometimes with Load Time Analyzer extension installed

Categories

(Core :: Layout, defect)

x86
Windows XP
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: martijn.martijn, Unassigned)

References

()

Details

(Keywords: crash, regression)

Crash Data

Attachments

(1 file)

I'm getting a crash sometimes on this site with the Load Time Analyzer extension installed, when I have multiple tabs simultaneously loading.

I have a sort of slimmed down version, that sometimes crashes with the steps to reproduce that I'll describe shortly.

Talkback ID: TB25963856X
nsCSSFrameConstructor::WipeContainingBlock  [mozilla\layout\base\nscssframeconstructor.cpp, line 12980]
nsCSSFrameConstructor::ContentAppended  [mozilla\layout\base\nscssframeconstructor.cpp, line 8891]
To reproduce:
- Install nightly tester tools (to be able to install Load Time Analyzer): -> http://users.blueprintit.co.uk/~dave/web/firefox/nightly
- Install Load Time Analyzer: -> https://addons.mozilla.org/firefox/3371/
- Extract attached testcase
- Open in 8 tabs
- Do a reload on all tabs
- Now switch tabs back and forth, while all the tabs are reloading, result -> crash
Keywords: testcase
FWIW, I see the performance problems, but not the crash with a recent trunk build.
I just had this crash without the Load Time Analyzer enabled, but with a load of other extensions installed, I suspect the Extended Statusbar 1.2.5 might be involved this time.
This is now worksforme, using current trunk build and doing the steps to reproduce.
I'm still seeing the performance problem, however.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
Oops, maybe I shouldn't have closed this bug? Maybe "the underlying problem is still there"?
Hard to tell, since we never figured out what that was.

Is there a separate bug on the performance issue?  That should be filed, and request blocking1.9.
Sorry, in fact, I don't see a performance regression issue at all, anymore, using current trunk build.

I'm just marking it worksforme, since nobody figured out why the crash was happening, and it doesn't happen anymore with current trunk build.
Crash Signature: [@ nsCSSFrameConstructor::WipeContainingBlock]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: