Closed Bug 43048 Opened 26 years ago Closed 24 years ago

Bringing up mail compose window throws FrameManager assertion

Categories

(MailNews Core :: Composition, defect, P3)

x86
Windows NT
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME
Future

People

(Reporter: kinmoz, Assigned: bugzilla)

Details

In my 06/19/00 debug build, I'm seeing the following assertion thrown when bringing up a message compose window because aContent is NULL. NTDLL! 77f762e8() nsDebug::Assertion(const char * 0x01f60784, const char * 0x01f60778, const char * 0x01f60744, int 481) line 242 + 13 bytes nsDebug::WarnIfFalse(const char * 0x01f60784, const char * 0x01f60778, const char * 0x01f60744, int 481) line 300 + 21 bytes FrameManager::GetPrimaryFrameFor(FrameManager * const 0x04e7f840, nsIContent * 0x00000000, nsIFrame * * 0x0012ec64) line 481 + 32 bytes PresShell::GetPrimaryFrameFor(const PresShell * const 0x04e7a130, nsIContent * 0x00000000, nsIFrame * * 0x0012ec64) line 3306 + 32 bytes nsTreeRowGroupFrame::IndexOfRow(nsIPresContext * 0x04e7af00, nsIContent * 0x00000000, int & -1) line 1847 nsTreeFrame::GetIndexOfItem(nsTreeFrame * const 0x02bdf32c, nsIPresContext * 0x04e7af00, nsIDOMElement * 0x05896f5c, int * 0x0012ee80) line 765 nsTreeBoxObject::GetIndexOfItem(nsTreeBoxObject * const 0x05baa480, nsIDOMElement * 0x05896f5c, int * 0x0012ee80) line 176 + 40 bytes XPTC_InvokeByIndex(nsISupports * 0x05baa480, unsigned int 8, unsigned int 2, nsXPTCVariant * 0x0012ee70) line 139 nsXPCWrappedNativeClass::CallWrappedMethod(JSContext * 0x04d64d90, nsXPCWrappedNative * 0x05bab850, const XPCNativeMemberDescriptor * 0x04507108, nsXPCWrappedNativeClass::CallMode CALL_METHOD, unsigned int 1, long * 0x04edc008, long * 0x0012f020) line 914 + 43 bytes WrappedNative_CallMethod(JSContext * 0x04d64d90, JSObject * 0x04ff06f8, unsigned int 1, long * 0x04edc008, long * 0x0012f020) line 200 + 34 bytes js_Invoke(JSContext * 0x04d64d90, unsigned int 1, unsigned int 0) line 686 + 23 bytes js_Interpret(JSContext * 0x04d64d90, long * 0x0012f9d8) line 2490 + 15 bytes js_Execute(JSContext * 0x04d64d90, JSObject * 0x03ad0be0, JSScript * 0x05baafb0, JSFunction * 0x00000000, JSStackFrame * 0x00000000, unsigned int 0, long * 0x0012f9d8) line 857 + 13 bytes JS_EvaluateUCScriptForPrincipals(JSContext * 0x04d64d90, JSObject * 0x03ad0be0, JSPrincipals * 0x014d9b14, const unsigned short * 0x0012fa94, unsigned int 14, const char * 0x05b9a470, unsigned int 379, long * 0x0012f9d8) line 2754 + 27 bytes nsJSContext::EvaluateString(nsJSContext * const 0x04d67220, const nsString & {...}, void * 0x03ad0be0, nsIPrincipal * 0x014d9b10, const char * 0x05b9a470, unsigned int 379, const char * 0x002fb468, nsString & {...}, int * 0x0012fa78) line 464 + 55 bytes GlobalWindowImpl::RunTimeout(nsTimeoutImpl * 0x05b9a530) line 3340 + 97 bytes nsGlobalWindow_RunTimeout(nsITimer * 0x05b9a410, void * 0x05b9a530) line 3605 + 15 bytes nsTimer::Fire() line 194 + 17 bytes nsTimerManager::FireNextReadyTimer(nsTimerManager * const 0x014e47f0, unsigned int 0) line 117 nsAppShell::Run(nsAppShell * const 0x01496190) line 116 nsAppShellService::Run(nsAppShellService * const 0x014957d0) line 387 main1(int 1, char * * 0x00c74c80, nsISupports * 0x00000000) line 906 + 32 bytes main(int 1, char * * 0x00c74c80) line 1092 + 37 bytes mainCRTStartup() line 338 + 17 bytes KERNEL32! 77f1b9ea()
Can you continue past the assertion? Asking so that I can mark nsbeta2 if needed.
Yes you can continue past it.
Jean-Francois, Does anything bad happen because of this?
Target Milestone: --- → M18
No, it's just a pain in a debug build!
Status: NEW → ASSIGNED
Moving to future milestone. If there is a bad end user visible behavior, please include that in the bug so we can reconsider.
Target Milestone: M18 → Future
I don't see anymore this assertion.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.