Closed Bug 76013 Opened 24 years ago Closed 24 years ago

crashes when using Next button (or F key) consecutively

Categories

(SeaMonkey :: MailNews: Message Display, defect)

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: fenella, Assigned: sspitzer)

Details

Linux (2001-04-13-05 trunk) Win32 (2001-04-13-06 trunk) Mac (2001-04-13-04 trunk) 1. Launch Mail 2. Select Inbox, click of Next to read unread messages consecutively, or use the F key Actual result: it crashes at the 7th or the 8th message on Win32, crashes at the 7th on Linux and about 3rd on Mac. Expected result: should not crash this occurs on all 3 platforms. Stack trace will come.
Fenella, do you have the stack trace? I was able to do this for about 40-50 messages consecutively without any problem using the 4/15 build.
Scott, I consistently saw it on the 4/13 builds. Here is the stack trace: Incident ID 29077679 ( and also Incident ID 29077823 ) Trigger Time 2001-04-13 17:33:27 Email Address fenella@netscape.com Client IP Address 208.12.40.42 User Comments using F (next message ) consecutively crashes (at the 8th times.) Build ID 2001041306 Product ID Netscape6.50 Platform ID Win32 Stack Trace nsCookieService::GetCookieStringFromHttp [d:\builds\seamonkey\mozilla\extensions\cookie\nsCookieService.cpp, line 140] nsCookieHTTPNotify::ModifyRequest [d:\builds\seamonkey\mozilla\extensions\cookie\nsCookieHTTPNotify.cpp, line 188] XPTC_InvokeByIndex [d:\builds\seamonkey\mozilla\xpcom\reflect\xptcall\src\md\win32\xptcinvoke.cpp, line 139] EventHandler [d:\builds\seamonkey\mozilla\xpcom\proxy\src\nsProxyEvent.cpp, line 510] nsProxyObject::Post [d:\builds\seamonkey\mozilla\xpcom\proxy\src\nsProxyEvent.cpp, line 450] nsProxyEventObject::CallMethod [d:\builds\seamonkey\mozilla\xpcom\proxy\src\nsProxyEventObject.cpp, line 431] PrepareAndDispatch [d:\builds\seamonkey\mozilla\xpcom\reflect\xptcall\src\md\win32\xptcstubs.cpp, line 102] SharedStub [d:\builds\seamonkey\mozilla\xpcom\reflect\xptcall\src\md\win32\xptcstubs.cpp, line 124] nsHTTPChannel::Connect [d:\builds\seamonkey\mozilla\netwerk\protocol\http\src\nsHTTPChannel.cpp, line 2076] nsHTTPChannel::OnCacheEntryAvailable [d:\builds\seamonkey\mozilla\netwerk\protocol\http\src\nsHTTPChannel.cpp, line 3487] XPTC_InvokeByIndex [d:\builds\seamonkey\mozilla\xpcom\reflect\xptcall\src\md\win32\xptcinvoke.cpp, line 139] EventHandler [d:\builds\seamonkey\mozilla\xpcom\proxy\src\nsProxyEvent.cpp, line 510] PL_HandleEvent [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c, line 589] PL_ProcessPendingEvents [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c, line 522] _md_EventReceiverProc [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c, line 1070]
QA Contact: esther → fenella
That would explain why it's not showing up in the 4/15 build because it got fixed 4/13 after the builds came out. Marking WFM.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Linux (2001-04-16-10 trunk) Win32 (2001-04-16-06 trunk) Mac (2001-04-16-04 trunk) The problem is no longer there.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.