Closed Bug 86644 Opened 23 years ago Closed 22 years ago

mozilla 0.9.1 or later crashes if old theme installed [@ nsCSSFrameConstructor::ConstructDocElementFrame]

Categories

(Core :: Layout, defect, P1)

defect

Tracking

()

RESOLVED DUPLICATE of bug 77716
mozilla1.0.1

People

(Reporter: s_kitching, Assigned: hyatt)

References

Details

(Keywords: crash)

Crash Data

I've been using mozilla0.9.0 for quite a while, with the "aqua" theme downlaoded
from themes.org. I recently tried to upgrade to 0.9.1 and found the new release
crashed immediately on startup (just after splash screen). [you will find
talkback dumps from simon.kitching@hutchison3g.com]. Same with later nightly builds.

After starting 0.9.0, switching back to Modern Theme, can now start nightly
2001061804 (and probably others). Aqua theme still appears in view|Apply Theme,
and will crash this build immediately when selected.
possible dup of bug 83414, which also refers to the aqua theme.
Severity: normal → critical
Keywords: crash
is this one of the theme crashers? 
Incident ID 31901342
Stack Signature nsCSSFrameConstructor::ConstructDocElementFrame 23a54783
Bug ID
Trigger Time 2001-06-19 02:59:32
User Comments unzipped nightly build with talkback. ran mozilla.exe splash
screen displayed, then crash.
Build ID 2001061809
Product ID MozillaTrunk
Platform ID Win32
Stack Trace
nsCSSFrameConstructor::ConstructDocElementFrame
[d:\builds\seamonkey\mozilla\layout\html\style\src\nsCSSFrameConstructor.cpp,
line 3320]
nsCSSFrameConstructor::ContentInserted
[d:\builds\seamonkey\mozilla\layout\html\style\src\nsCSSFrameConstructor.cpp,
line 8469]
StyleSetImpl::ContentInserted
[d:\builds\seamonkey\mozilla\content\base\src\nsStyleSet.cpp, line 1106]
PresShell::InitialReflow
[d:\builds\seamonkey\mozilla\layout\html\base\src\nsPresShell.cpp, line 2546]
HTMLContentSink::StartLayout
[d:\builds\seamonkey\mozilla\content\html\document\src\nsHTMLContentSink.cpp,
line 3511]
HTMLContentSink::OpenBody
[d:\builds\seamonkey\mozilla\content\html\document\src\nsHTMLContentSink.cpp,
line 2885]
CNavDTD::OpenBody [d:\builds\seamonkey\mozilla\htmlparser\src\CNavDTD.cpp, line
3127]
CNavDTD::OpenContainer [d:\builds\seamonkey\mozilla\htmlparser\src\CNavDTD.cpp,
line 3378]
CNavDTD::HandleDefaultStartToken
[d:\builds\seamonkey\mozilla\htmlparser\src\CNavDTD.cpp, line 1316]
CNavDTD::HandleStartToken
[d:\builds\seamonkey\mozilla\htmlparser\src\CNavDTD.cpp, line 1721]
CNavDTD::HandleToken [d:\builds\seamonkey\mozilla\htmlparser\src\CNavDTD.cpp,
line 901]
CNavDTD::BuildModel [d:\builds\seamonkey\mozilla\htmlparser\src\CNavDTD.cpp,
line 544]
nsParser::BuildModel [d:\builds\seamonkey\mozilla\htmlparser\src\nsParser.cpp,
line 1994]
nsParser::ResumeParse [d:\builds\seamonkey\mozilla\htmlparser\src\nsParser.cpp,
line 1873]
nsParser::OnStopRequest
[d:\builds\seamonkey\mozilla\htmlparser\src\nsParser.cpp, line 2353]
nsDocumentOpenInfo::OnStopRequest
[d:\builds\seamonkey\mozilla\uriloader\base\nsURILoader.cpp, line 255]
nsStreamIOChannel::OnStopRequest
[d:\builds\seamonkey\mozilla\netwerk\base\src\nsInputStreamChannel.cpp, line 461]
nsOnStopRequestEvent::HandleEvent
[d:\builds\seamonkey\mozilla\netwerk\base\src\nsRequestObserverProxy.cpp, line 161]
PL_HandleEvent [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c, line 591]
PL_ProcessPendingEvents [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c,
line 524]
_md_EventReceiverProc [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c, line
1072]
nsAppShellService::Run
[d:\builds\seamonkey\mozilla\xpfe\appshell\src\nsAppShellService.cpp, line 418]
main1 [d:\builds\seamonkey\mozilla\xpfe\bootstrap\nsAppRunner.cpp, line 1146]
main [d:\builds\seamonkey\mozilla\xpfe\bootstrap\nsAppRunner.cpp, line 1440]
WinMain [d:\builds\seamonkey\mozilla\xpfe\bootstrap\nsAppRunner.cpp, line 1458]
WinMainCRTStartup() 
*** Bug 84053 has been marked as a duplicate of this bug. ***
Marking NEW based on dupe. THe dupe occuried on Linux so changing OS/Platform 
appropriately..Trying Layout first though might be Frames.
Assignee: asa → karnaze
Status: UNCONFIRMED → NEW
Component: Browser-General → Layout
Ever confirmed: true
OS: Windows 2000 → All
QA Contact: doronr → petersen
Hardware: PC → All
*** Bug 88994 has been marked as a duplicate of this bug. ***
This bug prevents me from running ANY version of Mozilla! I tried uninstalling 
the Aqua theme from .9 but now neither .9.1 nor .9 nor .9.2 works. I'm dying 
for a fix as I'm stuck with Microshit again :-( Also, if anyone could tell me 
how to remove ALL install infos from my system so I can do a clean install, 
it'd be really appreciated. I tried reinstalling from zip, the uninstall that 
comes with .9.2, manually removing all registry entries containing Mozilla or 
anything like it, and any files I could find to be associated with Mozilla but 
it still won't work!!! Please anyone, help me out!
*** Bug 88965 has been marked as a duplicate of this bug. ***
ozzymartin@hotmail.com: 
create an new profile with "mozilla -profilemanager" or delete all files in your
"profile/Chrome" directory
Thanks Matti,

The ozzymartin@hotmail.com's workaround works well for me. 
Now I can enjoy faster and more stable 0.9.2 mozilla. :)
It is really much better than 0.9.1.

In my case (Windows 2000 environment), the "profile/Chrome" directory is
D:\Documents and Settings\<profile-id>\7b5s377l.slt\Cache because I have used
mozilla since 0.8 or later. In 0.9.2, the default user profile/chrome directory
is D:\Documents and Settings\<windows-user-id>\Application
Data\Mozilla\Profiles\<profile-id>\kxbd9pcg.slt\chrome.


taking to investigate.
Assignee: karnaze → attinasi
Priority: -- → P1
Target Milestone: --- → mozilla0.9.3
Target Milestone: mozilla0.9.3 → mozilla0.9.4
Just encountered this bug with 0.9.3 on win98.  Terrible

This is a horrible error.  Imagine your mom trying to install a new theme and
having mozilla crash so bad she can't even load it to uninstall the theme. 
She'll not know to delete certain files associated with her profile.

Shouldn't mozilla perform some sort of check to make sure the skin is functional
before crashing into oblivion, leaving users high and dry?  This may be the
penalty (the checker) for having custmizability.  Unfortunately, you can't rely
on 3rd party themers to make good themes.
Target Milestone: mozilla0.9.4 → mozilla1.0
I know, how to crate a new profile - that was the way I choosed.  But I guess
this is an error even if the user can avoid it.
reassigning to hyatt since he has the other crash bug on aqua themes (bug 83414)
Assignee: attinasi → hyatt
Status: NEW → ASSIGNED
Target Milestone: mozilla1.0 → mozilla1.0.1
Bug 77716 has same/similar crash signature.
Summary: mozilla 0.9.1 or later crashes if old theme installed → mozilla 0.9.1 or later crashes if old theme installed [@ nsCSSFrameConstructor::ConstructDocElementFrame]
this matches one of the signatures in that bug, and it matches one of the causes

listed for that bug.

*** This bug has been marked as a duplicate of 77716 ***
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Crash Signature: [@ nsCSSFrameConstructor::ConstructDocElementFrame]
You need to log in before you can comment on or make changes to this bug.