Closed
Bug 220346
Opened 21 years ago
Closed 21 years ago
Mozilla Crash with IMAP [@ nsUInt32Array::GetAt ]
Categories
(MailNews Core :: Backend, defect)
MailNews Core
Backend
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mjaber, Assigned: Bienvenu)
Details
(Keywords: crash, topcrash)
Crash Data
Attachments
(1 file)
1013 bytes,
patch
|
mscott
:
superreview+
dbaron
:
approval1.7b+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (X11; U; Linux i686; fr-FR; rv:1.4) Gecko/20030630
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; fr-FR; rv:1.4) Gecko/20030630
Hi,
I have a IMAP mail server ( exim ) on my personal machine ( on ADSL ).
As every day ip address change, I have a dyndns domain name to stay in touch
with my server.
Every time one IMAP folder is open ( with mail lis panel on it ), and the ip
change, mozilla report a connection timeout even if the dyndns domain is
refreshed ( is it a bug into a dns cache ? ) and if I try to see a particular
mail in that circonstances, mozilla seem to try to connect ( log is animated )
and after 1 or 2 minutes, mozilla report connection timeout or completely crash...
Reproducible: Sometimes
Steps to Reproduce:
1.open IMAP mailbox
2.change ip address of the server
3.try to open a mail into an IMAP folder
Actual Results:
after a long time mozilla report server connection Timeout or crash
Expected Results:
reconnect to the dns name and re-open IMAP connection to open message
Reporter | ||
Comment 1•21 years ago
|
||
This bug already exists into mozilla 1.3.1 ( mandrake security update version )
Comment 2•21 years ago
|
||
Could you retest it with 1.5 RC or with actual nightbuild?
Severity: major → critical
Keywords: crash
Comment 3•21 years ago
|
||
no, please try a Nightly build (1.6a)
They rewrote the whole DNS part (and disabled the caching)
This DNS reqrite is not in 1.5 branch
Reporter | ||
Comment 4•21 years ago
|
||
I just try the nightly build 1.6a and I've got the same result but faster....
see the feedback agent report : TB23903745E and TB23903619 ( Program Exception )
for more informations...
Comment 5•21 years ago
|
||
Stack trace from TB23903745E:
nsUInt32Array::GetAt()
nsMsgDBView::ApplyCommandToIndicesWithFolder()
nsMsgDBView::PerformActionOnJunkMsgs()
nsMsgDBView::OnMessageClassified()
nsBayesianFilter::observeMessage()
MessageObserver::analyzeTokens()
TokenStreamListener::OnStopRequest()
nsStreamConverter::OnStopRequest()
nsStreamListenerTee::OnStopRequest()
nsOnStopRequestEvent0::HandleEvent()
nsStreamListenerEvent0::HandlePLEvent()
PL_HandleEvent()
PL_ProcessPendingEvents()
nsEventQueueImpl::ProcessPendingEvents()
event_processor_callback()
our_gdk_io_invoke()
libglib-1.2.so.0 + 0x117d6 (0x402cd7d6)
libglib-1.2.so.0 + 0x143ee (0x402d03ee)
libglib-1.2.so.0 + 0x14199 (0x402d0199)
libglib-1.2.so.0 + 0x13174 (0x402cf174)
Comment 6•21 years ago
|
||
Stack from TB23903619 (seems to be a different crash):
0x08e237ac
nsHTMLIFrameElement::~nsHTMLIFrameElement()
nsHTMLIFrameElement::Release()
nsGenericHTMLContainerElement::~nsGenericHTMLContainerElement()
nsHTMLDivElement::~nsHTMLDivElement()
nsGenericElement::Release()
nsHTMLDivElement::Release()
nsGenericHTMLContainerElement::~nsGenericHTMLContainerElement()
nsHTMLBodyElement::~nsHTMLBodyElement()
nsGenericElement::Release()
nsHTMLBodyElement::Release()
SinkContext::End()
HTMLContentSink::~HTMLContentSink()
HTMLContentSink::Release()
nsParser::~nsParser()
nsParser::Release()
nsCOMPtr::assign_with_AddRef()
CSSLoaderImpl::SheetComplete()
CSSLoaderImpl::ParseSheet()
SheetLoadData::OnStreamComplete()
nsUnicharStreamLoader::OnStopRequest()
nsJARChannel::OnStopRequest()
nsInputStreamPump::OnStateStop()
nsInputStreamPump::OnInputStreamReady()
nsInputStreamReadyEvent::EventHandler()
PL_HandleEvent()
PL_ProcessPendingEvents()
nsEventQueueImpl::ProcessPendingEvents()
event_processor_callback()
our_gdk_io_invoke()
libglib-1.2.so.0 + 0x117d6 (0x402cd7d6)
libglib-1.2.so.0 + 0x143ee (0x402d03ee)
libglib-1.2.so.0 + 0x14199 (0x402d0199)
libglib-1.2.so.0 + 0x13174 (0x402cf174)
Updated•21 years ago
|
Summary: Mozilla Crash with IMAP → Mozilla Crash with IMAP [@ nsUInt32Array::GetAt ]
nsUInt32Array::GetAt
[c:/builds/seamonkey/mozilla/mailnews/base/util/nsUInt32Array.cpp line 144]
nsMsgDBView::CopyMessages
[c:/builds/seamonkey/mozilla/mailnews/base/src/nsMsgDBView.cpp line 2173]
nsMsgDBView::ApplyCommandToIndicesWithFolder
[c:/builds/seamonkey/mozilla/mailnews/base/src/nsMsgDBView.cpp line 2213]
nsMsgDBView::PerformActionOnJunkMsgs
[c:/builds/seamonkey/mozilla/mailnews/base/src/nsMsgDBView.cpp line 2764]
nsMsgDBView::OnMessageClassified
[c:/builds/seamonkey/mozilla/mailnews/base/src/nsMsgDBView.cpp line 2732]
Assignee | ||
Comment 9•21 years ago
|
||
check that the view index is valid
Assignee | ||
Updated•21 years ago
|
Attachment #143534 -
Flags: superreview?(mscott)
Comment 10•21 years ago
|
||
Comment on attachment 143534 [details] [diff] [review]
proposed fix
this could be a good 1.7b candidate
Attachment #143534 -
Flags: superreview?(mscott) → superreview+
Assignee | ||
Comment 11•21 years ago
|
||
Comment on attachment 143534 [details] [diff] [review]
proposed fix
yes, it's a pretty safe fix.
Attachment #143534 -
Flags: approval1.7b?
Attachment #143534 -
Flags: approval1.7b? → approval1.7b+
Assignee | ||
Updated•21 years ago
|
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Updated•20 years ago
|
Product: MailNews → Core
Comment 12•19 years ago
|
||
*** Bug 313103 has been marked as a duplicate of this bug. ***
Comment 13•19 years ago
|
||
*** Bug 315922 has been marked as a duplicate of this bug. ***
Comment 14•19 years ago
|
||
Crash occurs across platforms, setting All/All.
OS: Linux → All
Hardware: PC → All
Comment 15•19 years ago
|
||
This got 1.7b approval, was it checked in?
Assignee | ||
Comment 16•19 years ago
|
||
yes, afaik, it was. Is the same crash still occurring on trunk builds?
Comment 17•19 years ago
|
||
sure looks that way, i'd say those two bugs were poorly duped. if the bug was fixed as it claims in 2004, then bugs opened in late 2005 shouldn't be resolved as duplicates.
Comment 18•19 years ago
|
||
(In reply to comment #17)
> sure looks that way, i'd say those two bugs were poorly duped. if the bug was
> fixed as it claims in 2004, then bugs opened in late 2005 shouldn't be resolved
> as duplicates.
Whoops, my error. I completely missed the date differential here.
The crash is still happening (as evinced by the newer bugs) on the 1.5 branch, at least, if not the trunk.
Updated•17 years ago
|
Product: Core → MailNews Core
Updated•14 years ago
|
Crash Signature: [@ nsUInt32Array::GetAt ]
You need to log in
before you can comment on or make changes to this bug.
Description
•