Crash in operator new | nsImapProtocol::CreateNewLineFromSocket

NEW
Unassigned

Status

MailNews Core
Networking: IMAP
--
critical
2 years ago
a year ago

People

(Reporter: Richard Leger, Unassigned)

Tracking

({crash})

x86_64
Windows 7
crash

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [rare][need STR], crash signature)

User Story

from comment 3

user environment...
Win7 Pro 64bits
imap autosync DISALBED
roaming profile 
local network, IMAP server Cyrus 
Microsoft Security Essentials antivirus
(Reporter)

Description

2 years ago
This bug was filed from the Socorro interface and is 
report bp-13d36ccd-d1bc-4dfb-81db-2b77a2160726.
=============================================================

End-users opened email from IMAP Inbox by double clicking on it when Thunderbird crashed. Copy of email are not kept locally as per user account settings, so issue could have occurred while email was loaded/interpreted from the server.
(Reporter)

Updated

2 years ago
Hardware: x86 → x86_64
Version: unspecified → 45 Branch

Comment 1

2 years ago
bp-13d36ccd-d1bc-4dfb-81db-2b77a2160726.

0 	msvcr120.dll	operator new(unsigned int)
1 	xul.dll	nsImapProtocol::CreateNewLineFromSocket()
2 	xul.dll	nsImapServerResponseParser::GetNextLineForParser(char**)
3 	xul.dll	nsIMAPGenericParser::AdvanceToNextLine()
4 	xul.dll	nsImapServerResponseParser::msg_fetch_literal(bool, int)
5 	xul.dll	nsImapServerResponseParser::msg_fetch_content(bool, int, char const*)

I suspect bug 1294074 is related.
Perhaps also related to bug 1264302

Are these crashes reproducible?
Same users, or different users?
Component: General → Networking: IMAP
Product: Thunderbird → MailNews Core
See Also: → bug 1264302, bug 1294074
Version: 45 Branch → 45
(Reporter)

Comment 2

2 years ago
Crashes are random and not reproductable.
Same user. Though other users reported Thunderbird crash when browsing Inbox but not all seems to turn into a bug report...
I filed another one yesterday from another user with a different bug report if that can help. Copy of msg are not kept locally so when msg is clicked it is loaded it from the server.
(Reporter)

Comment 3

2 years ago
(In reply to Richard Leger from comment #2)
> I filed another one yesterday from another user with a different bug report
> if that can help. Copy of msg are not kept locally so when msg is clicked it
> is loaded it from the server.

Indeed bug 1294074 is the one I was referring to in my comment above... it belongs to one user on one machine.

bug 1294082 (this bug) and bug 1264302 belong to a different user on different machine (same brand/model though).

Both users using Thunderbird on Win7 Pro 64bits, IMAP account set not to keep copy of msg locally (so loaded in real time from server) and roaming profile (though end-user always use the same machine between crashes so rarely use the roaming feature). At time of crash, users are only connected once to their dedicated machine.

Both users on the same local network and using the same IMAP server Cyrus (connected on the same local network).

Both using Microsoft Anti-virus...

Comment 4

2 years ago
So this and the others are not related to dropbox as determined in bug 1285979?
Flags: needinfo?(richard.leger)
(Reporter)

Comment 5

2 years ago
Not related to Dropbox. This application is not present on the computer.

Updated

2 years ago
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: crash
Whiteboard: [rare][need STR]
Hi Richard.

You filed many bug reports recently (https://mzl.la/2jRRZPl full list). Many are probably related, if not the exact same problem. Appreciate the effort, but it's not worth filing many crash bug reports unless they are high volume or highly reproducible.  We don't have the manpower to respond to them.

Suggest it best to hang your hat on bug 1264302 (one which has higher crash rate for example).
And maybe get a person on version 52 beta in a couple weeks.
User Story: (updated)
Flags: needinfo?(richard.leger)
(Reporter)

Comment 7

a year ago
(In reply to Wayne Mery (:wsmwk, NI for questions) from comment #6)
> Hi Richard.
> 
> You filed many bug reports recently (https://mzl.la/2jRRZPl full list). Many
> are probably related, if not the exact same problem. Appreciate the effort,
> but it's not worth filing many crash bug reports unless they are high volume
> or highly reproducible.  We don't have the manpower to respond to them.
> 

So what is best to do then. Just send crash report with my email address without filling a bug?

> Suggest it best to hang your hat on bug 1264302 (one which has higher crash
> rate for example).
> And maybe get a person on version 52 beta in a couple weeks.

Yes I may have to move the two worth case on 52 beta... in the hope it helps... Is this version less likely to crash with IMAP email parsing on TB client that do not keep copy of msg on local computer?
You need to log in before you can comment on or make changes to this bug.