Closed Bug 127716 Opened 23 years ago Closed 23 years ago

chatzilla crash applying motif after mozilla theme switch - [@ 0x02cbe4a6 | 0x0440cd31 - nsHTMLLinkElement::SetDocument]

Categories

(Core :: XUL, defect)

Product:
Core
Component:
XUL
Platform:
x86
Windows 98
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
VERIFIED DUPLICATE of bug 129620
Milestone:
mozilla1.2alpha

People

(Reporter: cwhitt, Assigned: hyatt)

References

Details

(Keywords: crash, testcase, topcrash+)

Crash Data

Using build 2002021510 on win98se

Reproducibility: always

Steps to reproduce:
1. open mozilla navigator
2. open chatzilla
3. change theme in navigator
4. apply a motif under the view menu in chatzilla

Additionally, chatzilla looks very bad after a theme switch in moz, but I'm not
sure if this has to do with incomplete themes rather than a moz bug.
keyword: crash
Keywords: crash
I stated build ID 2002021510 in my initial report.  It should be 2002021503.

The crash doesn't occur when switching to the modern theme.
See talkback IDs:

TB3349384H
TB3350062E
TB3350280Y
TB3351142Z


Here's the most recent incident reported by Christopher:

 Incident ID 3351142   
Stack Signature  0x02cbe4a6 67c717f2
Trigger Time 2002-02-25 12:19:01
Email Address cwhitt@ieee.org
URL visited
Build ID 2002021510
Product ID MozillaTrunk
Platform
Operating System Win32
Module
Trigger Reason Access violation
User Comments yessiree - see bug 127716
Stack Trace
0x02cbe4a6
nsHTMLLinkElement::SetDocument
[d:\builds\seamonkey\mozilla\content\html\content\src\nsHTMLLinkElement.cpp,
line 106]
nsGenericElement::SetDocumentInChildrenOf
[d:\builds\seamonkey\mozilla\content\base\src\nsGenericElement.cpp, line 1408]
nsGenericElement::SetDocument
[d:\builds\seamonkey\mozilla\content\base\src\nsGenericElement.cpp, line 1475]
nsGenericHTMLElement::SetDocument
[d:\builds\seamonkey\mozilla\content\html\content\src\nsGenericHTMLElement.cpp,
line 1276]
nsGenericElement::SetDocumentInChildrenOf
[d:\builds\seamonkey\mozilla\content\base\src\nsGenericElement.cpp, line 1408]
nsGenericElement::SetDocument
[d:\builds\seamonkey\mozilla\content\base\src\nsGenericElement.cpp, line 1475]
nsGenericHTMLElement::SetDocument
[d:\builds\seamonkey\mozilla\content\html\content\src\nsGenericHTMLElement.cpp,
line 1276]
nsDocument::SetScriptGlobalObject
[d:\builds\seamonkey\mozilla\content\base\src\nsDocument.cpp, line 1510]
DocumentViewerImpl::Close
[d:\builds\seamonkey\mozilla\content\base\src\nsDocumentViewer.cpp, line 1374]
nsDocShell::SetupNewViewer
[d:\builds\seamonkey\mozilla\docshell\base\nsDocShell.cpp, line 4150]
nsDocShell::Embed [d:\builds\seamonkey\mozilla\docshell\base\nsDocShell.cpp,
line 3544]
nsDocShell::CreateContentViewer
[d:\builds\seamonkey\mozilla\docshell\base\nsDocShell.cpp, line 3921]
nsDSURIContentListener::DoContent
[d:\builds\seamonkey\mozilla\docshell\base\nsDSURIContentListener.cpp, line 108]
nsDocumentOpenInfo::DispatchContent
[d:\builds\seamonkey\mozilla\uriloader\base\nsURILoader.cpp, line 362]
nsDocumentOpenInfo::OnStartRequest
[d:\builds\seamonkey\mozilla\uriloader\base\nsURILoader.cpp, line 227]
nsJARChannel::OnStartRequest
[d:\builds\seamonkey\mozilla\netwerk\protocol\jar\src\nsJARChannel.cpp, line 588]
nsOnStartRequestEvent::HandleEvent
[d:\builds\seamonkey\mozilla\netwerk\base\src\nsRequestObserverProxy.cpp, line 162]
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]
KERNEL32.DLL + 0x24407 (0xbff94407)
0x00648c16 

Adding [@ 0x02cbe4a6 - nsHTMLLinkElement::SetDocument] to summary for tracking.
Summary: chatzilla crash applying motif after mozilla theme switch → chatzilla crash applying motif after mozilla theme switch - [@ 0x02cbe4a6 - nsHTMLLinkElement::SetDocument]
This is a problem in the theme switching code, not chatzilla.  Over to xptoolkit.
Assignee: rginda → jaggernaut
Component: chatzilla → XP Toolkit/Widgets
QA Contact: samuel → jrgm
-> hyatt
Assignee: jaggernaut → hyatt
Adding topcrash and testcase keyword.  This crash is being reported under
different stack signatures...so collectively, this has potential to be a
topcrash.  I have successfully reproduce this a few times.  Here is my most
recent incident:

 Incident ID 3498412   
Stack Signature  0x0440cd31 3a6e2e9a
Trigger Time 2002-02-28 18:53:00
Email Address jpatel@netscape.com
URL visited mail/news?
Build ID 2002022709
Product ID MozillaTrunk
Platform
Operating System Win32
Module
Trigger Reason Access violation
User Comments changed theme went to check email...just clicked on imap folder
and boom!
Stack Trace
0x0440cd31
nsHTMLLinkElement::SetDocument
[d:\builds\seamonkey\mozilla\content\html\content\src\nsHTMLLinkElement.cpp,
line 108]
nsGenericElement::SetDocumentInChildrenOf
[d:\builds\seamonkey\mozilla\content\base\src\nsGenericElement.cpp, line 1408]
nsGenericElement::SetDocument
[d:\builds\seamonkey\mozilla\content\base\src\nsGenericElement.cpp, line 1475]
nsGenericHTMLElement::SetDocument
[d:\builds\seamonkey\mozilla\content\html\content\src\nsGenericHTMLElement.cpp,
line 1276]
nsGenericElement::SetDocumentInChildrenOf
[d:\builds\seamonkey\mozilla\content\base\src\nsGenericElement.cpp, line 1408]
nsGenericElement::SetDocument
[d:\builds\seamonkey\mozilla\content\base\src\nsGenericElement.cpp, line 1475]
nsGenericHTMLElement::SetDocument
[d:\builds\seamonkey\mozilla\content\html\content\src\nsGenericHTMLElement.cpp,
line 1276]
nsDocument::SetScriptGlobalObject
[d:\builds\seamonkey\mozilla\content\base\src\nsDocument.cpp, line 1510]
DocumentViewerImpl::Close
[d:\builds\seamonkey\mozilla\content\base\src\nsDocumentViewer.cpp, line 1393]
nsDocShell::SetupNewViewer
[d:\builds\seamonkey\mozilla\docshell\base\nsDocShell.cpp, line 4144]
nsDocShell::Embed [d:\builds\seamonkey\mozilla\docshell\base\nsDocShell.cpp,
line 3536]
nsDocShell::CreateContentViewer
[d:\builds\seamonkey\mozilla\docshell\base\nsDocShell.cpp, line 3912]
nsDSURIContentListener::DoContent
[d:\builds\seamonkey\mozilla\docshell\base\nsDSURIContentListener.cpp, line 108]
nsDocumentOpenInfo::DispatchContent
[d:\builds\seamonkey\mozilla\uriloader\base\nsURILoader.cpp, line 362]
nsDocumentOpenInfo::OnStartRequest
[d:\builds\seamonkey\mozilla\uriloader\base\nsURILoader.cpp, line 227]
nsStreamIOChannel::OnStartRequest
[d:\builds\seamonkey\mozilla\netwerk\base\src\nsInputStreamChannel.cpp, line 470]
nsOnStartRequestEvent::HandleEvent
[d:\builds\seamonkey\mozilla\netwerk\base\src\nsRequestObserverProxy.cpp, line 162]
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] 

All I did was change the theme with a browser and mail window open...and then go
to click on an imap folder in the mail window.  Since the reporter crashed with
different steps...I'm guessing there are a few different ways to get to this crash.
Keywords: testcase, topcrash
Summary: chatzilla crash applying motif after mozilla theme switch - [@ 0x02cbe4a6 - nsHTMLLinkElement::SetDocument] → chatzilla crash applying motif after mozilla theme switch - [@ 0x02cbe4a6 | 0x0440cd31 - nsHTMLLinkElement::SetDocument]
perf bug 127784, dynamic theme switching is going to be disabled (try again 
another day).
Depends on: 127784
Target Milestone: --- → mozilla1.2
TB3833110M is my attempt to reproduce this with the latest 0.9.9 build,
2002-03-08 I think.  
This may have been fixed by the patch to bug 129620, which landed on branch and
trunk on 2002-03-08 (so it should be in the 3-9 builds, although the 3-9 trunk
builds would be broken for other reasons -- see bug 129827 and bug 129850).
Confirming dbaron's comments above.  This is fixed on the branch as of 20020309.
 I'll check the trunk after the regressions are fixed.
Making topcrash+.
Keywords: topcrash → topcrash+
Sounds like this is fixed.

*** This bug has been marked as a duplicate of 129620 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
This is the first chance I've had to get a new nightly since last weekend's
problematic builds.  I can no longer reproduce this.  Verifying.
Status: RESOLVED → VERIFIED
Crash Signature: [@ 0x02cbe4a6 | 0x0440cd31 - nsHTMLLinkElement::SetDocument]
You need to log in before you can comment on or make changes to this bug.