Closed Bug 1333031 Opened 8 years ago Closed 2 years ago

Crash in nsImapServerResponseParser::msg_fetch

Categories

(MailNews Core :: Networking: IMAP, defect)

Product:
MailNews Core
Component:
Networking: IMAP
Platform:
x86
All
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: richard.leger, Unassigned)

References

(
URL
)

Details

(Keywords: crash)

Crash Data

Attachments

(1 file)

TB.not.responding.after.upgrade.to.63.0.PNG
(deleted), image/png
Details
This bug was filed from the Socorro interface and is report bp-dc4f9fc2-b0f2-4738-982d-a45b52161031. ============================================================= User was going through Inbox search result... Email Preview Pane enabled. IMAP account Keep message for this account on this computer unticked.
bp-dc4f9fc2-b0f2-4738-982d-a45b52161031. 0 xul.dll nsImapServerResponseParser::msg_fetch() c:/builds/moz2_slave/tb-rel-c-esr45-w32_bld-0000000/build/mailnews/imap/src/nsImapServerResponseParser.cpp:1048 1 xul.dll nsImapServerResponseParser::response_data() c:/builds/moz2_slave/tb-rel-c-esr45-w32_bld-0000000/build/mailnews/imap/src/nsImapServerResponseParser.cpp:703 2 xul.dll nsImapServerResponseParser::ParseIMAPServerResponse(char const*, bool, char*) c:/builds/moz2_slave/tb-rel-c-esr45-w32_bld-0000000/build/mailnews/imap/src/nsImapServerResponseParser.cpp:206 3 xul.dll nsImapProtocol::ParseIMAPandCheckForNewMail(char const*, bool) c:/builds/moz2_slave/tb-rel-c-esr45-w32_bld-0000000/build/mailnews/imap/src/nsImapProtocol.cpp:1932 4 xul.dll nsImapProtocol::FetchMessage(nsCString const&, nsIMAPeFetchFields, char const*, unsigned int, unsigned int, char*) c:/builds/moz2_slave/tb-rel-c-esr45-w32_bld-0000000/build/mailnews/imap/src/nsImapProtocol.cpp:3572 5 xul.dll nsImapProtocol::FetchTryChunking(nsCString const&, nsIMAPeFetchFields, bool, char*, unsigned int, bool) c:/builds/moz2_slave/tb-rel-c-esr45-w32_bld-0000000/build/mailnews/imap/src/nsImapProtocol.cpp:3629 6 xul.dll nsIMAPBodypart::GeneratePart(nsIMAPBodyShell*, bool, bool) c:/builds/moz2_slave/tb-rel-c-esr45-w32_bld-0000000/build/mailnews/imap/src/nsIMAPBodyShell.cpp:461 7 xul.dll nsIMAPBodypartLeaf::Generate(nsIMAPBodyShell*, bool, bool) c:/builds/moz2_slave/tb-rel-c-esr45-w32_bld-0000000/build/mailnews/imap/src/nsIMAPBodyShell.cpp:602 8 xul.dll nsIMAPBodypartMultipart::Generate(nsIMAPBodyShell*, bool, bool) c:/builds/moz2_slave/tb-rel-c-esr45-w32_bld-0000000/build/mailnews/imap/src/nsIMAPBodyShell.cpp:1021 9 xul.dll nsIMAPBodypartMultipart::Generate(nsIMAPBodyShell*, bool, bool) c:/builds/moz2_slave/tb-rel-c-esr45-w32_bld-0000000/build/mailnews/imap/src/nsIMAPBodyShell.cpp:1021 10 xul.dll nsIMAPBodypartMessage::Generate(nsIMAPBodyShell*, bool, bool) c:/builds/moz2_slave/tb-rel-c-esr45-w32_bld-0000000/build/mailnews/imap/src/nsIMAPBodyShell.cpp:870 11 xul.dll nsIMAPBodyShell::Generate(char*) c:/builds/moz2_slave/tb-rel-c-esr45-w32_bld-0000000/build/mailnews/imap/src/nsIMAPBodyShell.cpp:266 12 xul.dll nsImapServerResponseParser::ProcessOkCommand(char const*) c:/builds/moz2_slave/tb-rel-c-esr45-w32_bld-0000000/build/mailnews/imap/src/nsImapServerResponseParser.cpp:424 13 xul.dll nsImapServerResponseParser::ParseIMAPServerResponse(char const*, bool, char*) c:/builds/moz2_slave/tb-rel-c-esr45-w32_bld-0000000/build/mailnews/imap/src/nsImapServerResponseParser.cpp:257 14 xul.dll nsImapProtocol::ParseIMAPandCheckForNewMail(char const*, bool) c:/builds/moz2_slave/tb-rel-c-esr45-w32_bld-0000000/build/mailnews/imap/src/nsImapProtocol.cpp:1932 15 xul.dll nsImapProtocol::FetchMessage(nsCString const&, nsIMAPeFetchFields, char const*, unsigned int, unsigned int, char*) c:/builds/moz2_slave/tb-rel-c-esr45-w32_bld-0000000/build/mailnews/imap/src/nsImapProtocol.cpp:3572 16 xul.dll nsImapProtocol::FetchTryChunking(nsCString const&, nsIMAPeFetchFields, bool, char*, unsigned int, bool) c:/builds/moz2_slave/tb-rel-c-esr45-w32_bld-0000000/build/mailnews/imap/src/nsImapProtocol.cpp:3629 17 xul.dll nsIMAPBodypart::GeneratePart(nsIMAPBodyShell*, bool, bool) c:/builds/moz2_slave/tb-rel-c-esr45-w32_bld-0000000/build/mailnews/imap/src/nsIMAPBodyShell.cpp:461 This may be the same issue of bug 1264302
Status: UNCONFIRMED → NEW
Component: Folder and Message Lists → Networking: IMAP
Depends on: 1264302
Ever confirmed: true
Product: Thunderbird → MailNews Core
Keywords: crash
Richard, Did you get a clear reduction in crash rate in version 60.0? This depended on bug 1264302 which got duped to bug 1216951, which was fixed in version 60.0 but the signature continued in version 60.0. And crash rate is up slightly in the last two months. (compared to May and June) However, the good news is there are no crashes in 60.2.1 and newer betas (newer than 60.0b11). So something other than bug 1216951 had an impact
Flags: needinfo?(richard.leger)
Well I had three crashes in the past month or so with 60.0b11... and a lot of issues... the start-up slow down is back and I endure some slow down with the interface... or when typing sometimes... last week I also set to download/cache 3 days worth of email into local cache via my main IMAP/SMTP account because I had multiple issues to load message contents (mostly slowdown)... One of the crash below but I don't remember which happens while I was not even using the application... would not recall exactly what I was doing when all of those occurred... I may have or not indicated in the note of the crash report... one of them was related to address-book contact search I believe... bp-752e4e8d-e81b-411e-9513-3619b0181003 03/10/2018 10:19 bp-8017d419-a7d9-47ba-ba11-f9a3a0181002 02/10/2018 20:53 bp-9810974d-16ba-479a-aec8-4fdbe0180910 10/09/2018 17:50 Hope that help.
Flags: needinfo?(richard.leger)
I attempted an upgrade to 63.0 but situation has gone worth... TB is in processing/not responding mode for about 10mn now... if I click on menu items they eventually come up on screen so TB is not frozen just very slow... so slow that it cannot be used!!! In activity manager is seems to say connection to server time out about 10mn ago... while I check the server is online and running fine... so not sure what is going on... this follow automatic restart of TB after applying update via the Help > About menu... I am attaching the screen shot... the menu also won't disappear from screen!!! Nor the menu button be accessible...
TB in processing/not responding mode after upgrade to 63.0beta version...
After trying in safe mode the issue seems not re-appearing. So I disabled the Lightning 6.5 add-on (last updated 29/10) which was the only one enabled, and now Thunderbird is opening fine! I guess the app boot-up issue may be related to the add-on then...
I meant TB version 63.0beta...
Updated to TB version 64.0b1 (32bits)... (from previously 63.0b1)... same slowness processing/not responding issue...
I opened a separate bug report for the issue I reported... bug 1502923
(In reply to Richard Leger from comment #3) > last week I also set to > download/cache 3 days worth of email into local cache via my main IMAP/SMTP > account because I had multiple issues to load message contents (mostly > slowdown)... Wayne, just to let you know, I have reverted back the setting I changed last week to no longer cache IMAP email following upgrade to 64.0b1... do to be in similar setup as previously... I will let you know if TB crash again... I just noticed that TB 64.0b1 seems to close by itself without crashing... not sure exactly how would that happens... seems to noticed couple of time that TB was closed after wake up from sleep on several occasion... while I am convince I let it opened when it went to sleep... but I can't be sure it closed before sleep while I was not using it... and I haven't figured out a re-producible case... I will also try to pay attention to make sure it was not a user error :-)
(Thanks for the feedback. In reply to Richard Leger from comment #3) > ... one of them was related to address-book contact search I believe... that would be this.... > bp-752e4e8d-e81b-411e-9513-3619b0181003 is Bug 1344897 - where you composing a message? we'll let this slide for now > bp-8017d419-a7d9-47ba-ba11-f9a3a0181002 @ shutdownhang | ntdll.dll@0x6a28c > bp-9810974d-16ba-479a-aec8-4fdbe0180910 @ shutdownhang | ntdll.dll@0x6be8c > I just noticed that TB 64.0b1 seems to close by itself without crashing... not sure exactly how would that happens... > seems to noticed couple of time that TB was closed after wake up from sleep on several occasion perhaps related to getting new mail, which is not surprising in your case
(In reply to Wayne Mery (:wsmwk) from comment #11) > > In reply to Richard Leger from comment #3) > > ... one of them was related to address-book contact search I believe... > > that would be this.... > > > bp-752e4e8d-e81b-411e-9513-3619b0181003 > is Bug 1344897 - where you composing a message? When composing message and looking up recipients, no issue. When opening TB addressbook and typing 'mar' in quick search field, TB crash. Here is a new crash report from TB 64.0b1 where same issue still occurs: bp-e70a05bc-dd42-44b5-8793-b09b50181101

(In reply to Richard Leger from comment #12)

(In reply to Wayne Mery (:wsmwk) from comment #11)

In reply to Richard Leger from comment #3)

... one of them was related to address-book contact search I believe...

that would be this....

bp-752e4e8d-e81b-411e-9513-3619b0181003
is Bug 1344897 - where you composing a message?

When composing message and looking up recipients, no issue.
When opening TB addressbook and typing 'mar' in quick search field, TB crash.

Here is a new crash report from TB 64.0b1 where same issue still occurs: bp-e70a05bc-dd42-44b5-8793-b09b50181101

Yeah, not this bug. See Bug 1344897 - Crash in nsldapi_find_in_cb_pollfds and nsAbQueryLDAPMessageListener::OnLDAPMessageSearchResult

Richard, what are your current crash signatures?

Rougly only 4 beta crashes in 3 months
Thunderbird 67.0b0 2
Thunderbird 68.0b0 2

Potentially helped by fixes from these bugs? (Which Richard has also seen)
Bug 1333038 fixed TB65+TB60 - Crash in nsMsgLineStreamBuffer::ReadNextLine
Bug 1216951 fixed TB60 - Signature verification failing for blank lines in chunked base64 attachment

Flags: needinfo?(richard.leger)
Whiteboard: [rare]

FYI, my recent crash reports... from TB 67.0b3 (64-bit)... I have not yet upgraded to 68.0 Beta 1...

bp-79211dc8-a717-401a-81df-415f40190711 11/07/2019, 12:27 <-- this one was a crash from April I believe that I just submitted for info...
bp-f3239349-a2ed-4fdc-9a50-e80390190621 21/06/2019, 09:28
bp-f43d1f2d-0bee-437a-a26b-1ea980190325 25/03/2019, 14:16
bp-8a14849d-581b-435b-97b6-6f4400190318 18/03/2019, 10:29

Flags: needinfo?(richard.leger)

bp-f3239349-a2ed-4fdc-9a50-e80390190621 is Bug 847356 - crash in PR_EnterMonitor via nsImapProtocol::GetPseudoInterrupted | nsIMAPBodypartMultipart::Generate

Two of the others are Bug 1517464 - Thunderbird crash in nsXPCWrappedJS::Release sending mail (or saving to Sent or Drafts)

On a daily basis, are you currently using beta? Or release?

Flags: needinfo?(richard.leger)
See Also: → https://bugzilla.mozilla.org/show_bug.cgi?id=1517464, https://bugzilla.mozilla.org/show_bug.cgi?id=847356

Currently using beta on daily bases...

Flags: needinfo?(richard.leger)

Similar stack for strlen | nsImapServerResponseParser::msg_fetch_literal bp-c3529356-c9a4-426a-a774-686120200122

Crash Signature: [@ nsImapServerResponseParser::msg_fetch] → [@ nsImapServerResponseParser::msg_fetch] [@ strlen | nsImapServerResponseParser::msg_fetch_literal]

the combination of signatures is not rare - ranks approx top 50

nsImapServerResponseParser::msg_fetch_content bp-84fd22f6-dfd2-4680-9f79-e38fc0200521
0 xul.dll nsImapServerResponseParser::msg_fetch_content(bool, int, char const*) comm/mailnews/imap/src/nsImapServerResponseParser.cpp:1856 context
1 xul.dll nsImapServerResponseParser::mime_part_data() comm/mailnews/imap/src/nsImapServerResponseParser.cpp:2311 cfi
2 xul.dll nsImapServerResponseParser::msg_fetch() comm/mailnews/imap/src/nsImapServerResponseParser.cpp:0 cfi
3 xul.dll nsImapServerResponseParser::response_data() comm/mailnews/imap/src/nsImapServerResponseParser.cpp:653 cfi
4 xul.dll nsImapServerResponseParser::ParseIMAPServerResponse(char const*, bool, char*) comm/mailnews/imap/src/nsImapServerResponseParser.cpp:188 cfi
5 xul.dll nsImapProtocol::ParseIMAPandCheckForNewMail(char const*, bool) comm/mailnews/imap/src/nsImapProtocol.cpp:1911 cfi
6 xul.dll nsImapProtocol::FetchMessage(nsTString<char> const&, nsIMAPeFetchFields, char const*, unsigned int, unsigned int, char*) comm/mailnews/imap/src/nsImapProtocol.cpp:3591 cfi
7 xul.dll nsImapProtocol::FetchTryChunking(nsTString<char> const&, nsIMAPeFetchFields, bool, char*, unsigned int, bool) comm/mailnews/imap/src/nsImapProtocol.cpp:3637 cfi
8 xul.dll nsIMAPBodypart::GeneratePart(nsIMAPBodyShell*, bool, bool) comm/mailnews/imap/src/nsIMAPBodyShell.cpp:413 cfi
9 xul.dll nsIMAPBodypartLeaf::Generate(nsIMAPBodyShell*, bool, bool) comm/mailnews/imap/src/nsIMAPBodyShell.cpp:529 cfi
10 xul.dll nsIMAPBodypartMultipart::Generate(nsIMAPBodyShell*, bool, bool) comm/mailnews/imap/src/nsIMAPBodyShell.cpp:894 cfi
11 xul.dll nsIMAPBodypartMultipart::Generate(nsIMAPBodyShell*, bool, bool) comm/mailnews/imap/src/nsIMAPBodyShell.cpp:894 cfi
12 xul.dll nsIMAPBodypartMultipart::Generate(nsIMAPBodyShell*, bool, bool) comm/mailnews/imap/src/nsIMAPBodyShell.cpp:894 cfi
13 xul.dll nsIMAPBodypartMessage::Generate(nsIMAPBodyShell*, bool, bool) comm/mailnews/imap/src/nsIMAPBodyShell.cpp:765 cfi
14 xul.dll nsIMAPBodyShell::Generate(char*) comm/mailnews/imap/src/nsIMAPBodyShell.cpp:228 cfi
15 xul.dll nsImapProtocol::ProcessSelectedStateURL() comm/mailnews/imap/src/nsImapProtocol.cpp:2724 cfi
16 xul.dll nsImapProtocol::ProcessCurrentURL() comm/mailnews/imap/src/nsImapProtocol.cpp:1765 cfi
17 xul.dll nsImapProtocol::ImapThreadMainLoop() comm/mailnews/imap/src/nsImapProtocol.cpp:1427 cfi
18 xul.dll nsImapProtocol::Run() comm/mailnews/imap/src/nsImapProtocol.cpp:1110 cfi
19 xul.dll nsThread::ProcessNextEvent(bool, bool*) xpcom/threads/nsThread.cpp:1175

strlen | nsImapServerResponseParser::msg_fetch
bp-03b8b5a2-4dce-48db-99b6-3eff80200520
0 ucrtbase.dll strlen
1 xul.dll nsImapServerResponseParser::msg_fetch() comm/mailnews/imap/src/nsImapServerResponseParser.cpp:962
2 xul.dll nsImapServerResponseParser::response_data() comm/mailnews/imap/src/nsImapServerResponseParser.cpp:653
3 xul.dll nsImapServerResponseParser::ParseIMAPServerResponse(char const*, bool, char*) comm/mailnews/imap/src/nsImapServerResponseParser.cpp:188
4 xul.dll nsImapProtocol::ParseIMAPandCheckForNewMail(char const*, bool) comm/mailnews/imap/src/nsImapProtocol.cpp:1911
5 xul.dll nsImapProtocol::FetchMessage(nsTString<char> const&, nsIMAPeFetchFields, char const*, unsigned int, unsigned int, char*) comm/mailnews/imap/src/nsImapProtocol.cpp:3591
6 xul.dll nsImapProtocol::FetchTryChunking(nsTString<char> const&, nsIMAPeFetchFields, bool, char*, unsigned int, bool) comm/mailnews/imap/src/nsImapProtocol.cpp:3637
7 xul.dll nsIMAPBodypart::GeneratePart(nsIMAPBodyShell*, bool, bool) comm/mailnews/imap/src/nsIMAPBodyShell.cpp:413
8 xul.dll nsIMAPBodypartLeaf::Generate(nsIMAPBodyShell*, bool, bool) comm/mailnews/imap/src/nsIMAPBodyShell.cpp:529
9 xul.dll nsIMAPBodypartMultipart::Generate(nsIMAPBodyShell*, bool, bool) comm/mailnews/imap/src/nsIMAPBodyShell.cpp:894
10 xul.dll nsIMAPBodypartMultipart::Generate(nsIMAPBodyShell*, bool, bool) comm/mailnews/imap/src/nsIMAPBodyShell.cpp:894
11 xul.dll nsIMAPBodypartMessage::Generate(nsIMAPBodyShell*, bool, bool) comm/mailnews/imap/src/nsIMAPBodyShell.cpp:765
12 xul.dll nsIMAPBodyShell::Generate(char*) comm/mailnews/imap/src/nsIMAPBodyShell.cpp:228
13 xul.dll nsImapProtocol::ProcessSelectedStateURL() comm/mailnews/imap/src/nsImapProtocol.cpp:2724
14 xul.dll nsImapProtocol::ProcessCurrentURL() comm/mailnews/imap/src/nsImapProtocol.cpp:1765
15 xul.dll nsImapProtocol::ImapThreadMainLoop() comm/mailnews/imap/src/nsImapProtocol.cpp:1427
16 xul.dll nsImapProtocol::Run() comm/mailnews/imap/src/nsImapProtocol.cpp:1110

Crash Signature: [@ nsImapServerResponseParser::msg_fetch] [@ strlen | nsImapServerResponseParser::msg_fetch_literal] → [@ nsImapServerResponseParser::msg_fetch] [@ strlen | nsImapServerResponseParser::msg_fetch_literal] [@ strlen | nsImapServerResponseParser::msg_fetch ] [@ nsImapServerResponseParser::msg_fetch_content ]
OS: Windows 7 → All
Whiteboard: [rare]

Crash rate overall is down 50% compared to 6 months ago, which was in July/summer. Which should mean the crash rate dropped way more than 50% compared to a year ago.

Richard, Do you still get this crash signature when using version 78?

Flags: needinfo?(richard.leger)
Flags: needinfo?(vseerror)

(In reply to Wayne Mery (:wsmwk) from comment #21)

Crash rate overall is down 50% compared to 6 months ago, which was in July/summer. Which should mean the crash rate dropped way more than 50% compared to a year ago.

Richard, Do you still get this crash signature when using version 78?

Currently using Beta version just upgraded to TB 85.0b3 (64-bit), here is a list of my recent crashes related to recent version of Beta, if that can be of any help at all...

bp-caeeeef2-d80c-4255-947e-6ebc50201229 29/12/2020, 18:49
bp-cdcd04b4-edc3-44e4-aea2-4dfc00201203 03/12/2020, 21:49
bp-236423df-3725-4125-bff0-0fee90201118 18/11/2020, 10:25
bp-65e35416-9b03-467d-84b9-4a9950201104 04/11/2020, 08:06
bp-fd615056-10c2-4297-a3ed-9b8400201029 29/10/2020, 14:32
bp-4c5ec036-9077-457d-82f2-784d60201029 29/10/2020, 13:28
bp-1374061c-b8c4-4086-8b81-8ff8d0201028 28/10/2020, 16:40
bp-a2e84fe4-26f2-44e0-9ad4-0a9140201028 28/10/2020, 15:56

I will try to run 78 version for a couple of days next week see if it crashes but no promise...

Flags: needinfo?(richard.leger)
Flags: needinfo?(vseerror)

Version 78.14.0 crash rank ~#170. Version 91.2.1 significantly dropped, is beyond 300.

Severity: critical → S3
Flags: needinfo?(vseerror)

Version 91.2.1 significantly dropped, is beyond 300.

91.3.0 the same - all four signatures still exist

nsImapServerResponseParser::msg_fetch bp-10846f5f-13a7-4559-9be7-eccb10211109
0 xul.dll nsImapServerResponseParser::msg_fetch() comm/mailnews/imap/src/nsImapServerResponseParser.cpp:935
1 xul.dll nsImapServerResponseParser::response_data() comm/mailnews/imap/src/nsImapServerResponseParser.cpp:643
2 xul.dll nsImapServerResponseParser::ParseIMAPServerResponse(char const*, bool, char*) comm/mailnews/imap/src/nsImapServerResponseParser.cpp:189
3 xul.dll nsImapProtocol::ParseIMAPandCheckForNewMail(char const*, bool) comm/mailnews/imap/src/nsImapProtocol.cpp:2031
4 xul.dll nsImapProtocol::FetchMessage(nsTString<char> const&, <unnamed-tag>, char const*, unsigned int, unsigned int, char*) comm/mailnews/imap/src/nsImapProtocol.cpp:3715
5 xul.dll nsImapProtocol::FetchTryChunking(nsTString<char> const&, <unnamed-tag>, bool, char*, unsigned int, bool) comm/mailnews/imap/src/nsImapProtocol.cpp:3765
6 xul.dll nsIMAPBodypart::GeneratePart(nsImapBodyShell*, bool, bool) comm/mailnews/imap/src/nsImapBodyShell.cpp:409
7 xul.dll nsIMAPBodypartLeaf::Generate(nsImapBodyShell*, bool, bool) comm/mailnews/imap/src/nsImapBodyShell.cpp:528
8 xul.dll nsIMAPBodypartMultipart::Generate(nsImapBodyShell*, bool, bool) comm/mailnews/imap/src/nsImapBodyShell.cpp:889
9 xul.dll nsIMAPBodypartMultipart::Generate(nsImapBodyShell*, bool, bool) comm/mailnews/imap/src/nsImapBodyShell.cpp:889
10 xul.dll nsIMAPBodypartMultipart::Generate(nsImapBodyShell*, bool, bool) comm/mailnews/imap/src/nsImapBodyShell.cpp:889
11 xul.dll nsIMAPBodypartMessage::Generate(nsImapBodyShell*, bool, bool) comm/mailnews/imap/src/nsImapBodyShell.cpp:760
12 xul.dll nsImapBodyShell::Generate(char*) comm/mailnews/imap/src/nsImapBodyShell.cpp:224

strlen | nsImapServerResponseParser::msg_fetch_literal bp-6a459a92-113d-4ff3-af2c-9edd40211109
0 ucrtbase.dll strlen
1 xul.dll nsImapServerResponseParser::msg_fetch_literal(bool, int) comm/mailnews/imap/src/nsImapServerResponseParser.cpp:2722
2 xul.dll nsImapServerResponseParser::msg_fetch_content(bool, int, char const*) comm/mailnews/imap/src/nsImapServerResponseParser.cpp:1860
3 xul.dll nsImapServerResponseParser::msg_fetch() comm/mailnews/imap/src/nsImapServerResponseParser.cpp:1163
4 xul.dll nsImapServerResponseParser::response_data() comm/mailnews/imap/src/nsImapServerResponseParser.cpp:643
5 xul.dll nsImapServerResponseParser::ParseIMAPServerResponse(char const*, bool, char*) comm/mailnews/imap/src/nsImapServerResponseParser.cpp:189
6 xul.dll nsImapProtocol::ParseIMAPandCheckForNewMail(char const*, bool) comm/mailnews/imap/src/nsImapProtocol.cpp:2031
7 xul.dll nsImapProtocol::FetchMessage(nsTString<char> const&, <unnamed-tag>, char const*, unsigned int, unsigned int, char*) comm/mailnews/imap/src/nsImapProtocol.cpp:3715
8 xul.dll nsImapProtocol::FetchTryChunking(nsTString<char> const&, <unnamed-tag>, bool, char*, unsigned int, bool) comm/mailnews/imap/src/nsImapProtocol.cpp:3765
9 xul.dll nsImapProtocol::FallbackToFetchWholeMsg(nsTString<char> const&, unsigned int) comm/mailnews/imap/src/nsImapProtocol.cpp:3477
10 xul.dll nsImapBodyShell::Generate(char*) comm/mailnews/imap/src/nsImapBodyShell.cpp:188

strlen | nsImapServerResponseParser::msg_fetch bp-0ba6cf2e-cff5-437b-95f0-7b9a50211109
0 ucrtbase.dll strlen
1 xul.dll nsImapServerResponseParser::msg_fetch() comm/mailnews/imap/src/nsImapServerResponseParser.cpp:961
2 xul.dll nsImapServerResponseParser::response_data() comm/mailnews/imap/src/nsImapServerResponseParser.cpp:643
3 xul.dll nsImapServerResponseParser::ParseIMAPServerResponse(char const*, bool, char*) comm/mailnews/imap/src/nsImapServerResponseParser.cpp:189
4 xul.dll nsImapProtocol::ParseIMAPandCheckForNewMail(char const*, bool) comm/mailnews/imap/src/nsImapProtocol.cpp:2031
5 xul.dll nsImapProtocol::FetchMessage(nsTString<char> const&, <unnamed-tag>, char const*, unsigned int, unsigned int, char*) comm/mailnews/imap/src/nsImapProtocol.cpp:3715
6 xul.dll nsImapProtocol::FetchTryChunking(nsTString<char> const&, <unnamed-tag>, bool, char*, unsigned int, bool) comm/mailnews/imap/src/nsImapProtocol.cpp:3765
7 xul.dll nsIMAPBodypart::GeneratePart(nsImapBodyShell*, bool, bool) comm/mailnews/imap/src/nsImapBodyShell.cpp:409
8 xul.dll nsIMAPBodypartLeaf::Generate(nsImapBodyShell*, bool, bool) comm/mailnews/imap/src/nsImapBodyShell.cpp:528
9 xul.dll nsIMAPBodypartMultipart::Generate(nsImapBodyShell*, bool, bool) comm/mailnews/imap/src/nsImapBodyShell.cpp:889
10 xul.dll nsIMAPBodypartMultipart::Generate(nsImapBodyShell*, bool, bool) comm/mailnews/imap/src/nsImapBodyShell.cpp:889
11 xul.dll nsIMAPBodypartMessage::Generate(nsImapBodyShell*, bool, bool) comm/mailnews/imap/src/nsImapBodyShell.cpp:760
12 xul.dll nsImapBodyShell::Generate(char*) comm/mailnews/imap/src/nsImapBodyShell.cpp:224

nsImapServerResponseParser::msg_fetch_content bp-c8b5e5ad-28d5-4998-ab80-a32860211109
0 xul.dll nsImapServerResponseParser::msg_fetch_content(bool, int, char const*) comm/mailnews/imap/src/nsImapServerResponseParser.cpp:1853
1 xul.dll nsImapServerResponseParser::msg_fetch() comm/mailnews/imap/src/nsImapServerResponseParser.cpp:1163
2 xul.dll nsImapServerResponseParser::response_data() comm/mailnews/imap/src/nsImapServerResponseParser.cpp:643
3 xul.dll nsImapServerResponseParser::ParseIMAPServerResponse(char const*, bool, char*) comm/mailnews/imap/src/nsImapServerResponseParser.cpp:189
4 xul.dll nsImapProtocol::ParseIMAPandCheckForNewMail(char const*, bool) comm/mailnews/imap/src/nsImapProtocol.cpp:2031
5 xul.dll nsImapProtocol::FetchMessage(nsTString<char> const&, <unnamed-tag>, char const*, unsigned int, unsigned int, char*) comm/mailnews/imap/src/nsImapProtocol.cpp:3715
6 xul.dll nsImapProtocol::FetchTryChunking(nsTString<char> const&, <unnamed-tag>, bool, char*, unsigned int, bool) comm/mailnews/imap/src/nsImapProtocol.cpp:3765
7 xul.dll nsImapProtocol::FallbackToFetchWholeMsg(nsTString<char> const&, unsigned int) comm/mailnews/imap/src/nsImapProtocol.cpp:3477
8 xul.dll nsImapBodyShell::Generate(char*) comm/mailnews/imap/src/nsImapBodyShell.cpp:188

Flags: needinfo?(vseerror)

I tried to duplicate but couldn't. Also, replied to https://support.mozilla.org/en-US/questions/1355351 (referenced above) to get more info about crashes from that reporter.

Flags: needinfo?(gds)

(In reply to gene smith from comment #28)

I tried to duplicate but couldn't. Also, replied to https://support.mozilla.org/en-US/questions/1355351 (referenced above) to get more info about crashes from that reporter.

Thanks. No response so far. I've just attempted again to contact the reporter.

Richard, with Bug 1742991 - crash nsXPCWrappedJS::AddRef - fixed in beta 96.0.b3 on Dec 20, I would hope your situation has improved.

How has it been for the past month?

(In reply to Richard Leger from comment #18)

Currently using beta on daily bases...

(In reply to Wayne Mery (:wsmwk) from comment #23)

Flags: needinfo?(richard.leger)

Also, what setting are you using for mime_parts_on_demand ?
See Bug 1673093 - Download large attachment fails, saved as 27 or 45 bytes, when offline store (mbox/maildir) not used and message/attachment too large to fit in cache RAM/memory and mail.server.default.mime_parts_on_demand=false. workaround: mime_parts_on_demand=true

(In reply to Wayne Mery (:wsmwk) from comment #31)

Also, what setting are you using for mime_parts_on_demand ?
See Bug 1673093 - Download large attachment fails, saved as 27 or 45 bytes, when offline store (mbox/maildir) not used and message/attachment too large to fit in cache RAM/memory and mail.server.default.mime_parts_on_demand=false. workaround: mime_parts_on_demand=true

I use the default: mail.server.default.mime_parts_on_demand=false

(In reply to Wayne Mery (:wsmwk) from comment #30)

Richard, with Bug 1742991 - crash nsXPCWrappedJS::AddRef - fixed in beta 96.0.b3 on Dec 20, I would hope your situation has improved.
How has it been for the past month?

Past months have been ok... but I just realised that I had enabled 3 days worth of caching on Inbox... (which seems very hard to disable in TB Beta 97.0b3) so I will disable again and see how it goes in TB Beta 97.0b3+ keeping mail.server.default.mime_parts_on_demand=false (default). If the bug is still present that should trigger it... in theory unless fixed :-) I'll do the same in 91ESR I use in parallel...

My most recent crashes fyi:
bp-e474fa4d-eea0-4a90-a3d6-2f99e1211223 23/12/2021, 19:03
bp-153ff11b-1179-4151-8607-eeacc0211105 05/11/2021, 11:02
bp-4c49f26a-881c-4c63-b7bd-a2d0f0211104 04/11/2021, 15:11

Flags: needinfo?(richard.leger)

No beta crashes in last five months.. And no version 102 crashes. Hopefully you have none?

  • bp-9d606a32-1fbf-4b86-8b78-abb760220904 91.13.0
    0 ucrtbase.dll strlen
    1 xul.dll nsImapServerResponseParser::msg_fetch_literal(bool, int) mailnews/imap/src/nsImapServerResponseParser.cpp:2722
    2 xul.dll nsImapServerResponseParser::msg_fetch_content(bool, int, char const*) mailnews/imap/src/nsImapServerResponseParser.cpp:1860
    3 xul.dll nsImapServerResponseParser::mime_part_data() mailnews/imap/src/nsImapServerResponseParser.cpp:2313
    4 xul.dll nsImapServerResponseParser::msg_fetch() mailnews/imap/src/nsImapServerResponseParser.cpp:1163
    5 xul.dll nsImapServerResponseParser::response_data() mailnews/imap/src/nsImapServerResponseParser.cpp:643
    6 xul.dll nsImapServerResponseParser::ParseIMAPServerResponse(char const*, bool, char*) mailnews/imap/src/nsImapServerResponseParser.cpp:189
    7 xul.dll nsImapProtocol::ParseIMAPandCheckForNewMail(char const*, bool) mailnews/imap/src/nsImapProtocol.cpp:2058
    8 xul.dll nsImapProtocol::FetchMessage(nsTString<char> const&, <unnamed-tag>, char const*, unsigned int, unsigned int, char*) mailnews/imap/src/nsImapProtocol.cpp:3742
    9 xul.dll nsImapProtocol::FetchTryChunking(nsTString<char> const&, <unnamed-tag>, bool, char*, unsigned int, bool) mailnews/imap/src/nsImapProtocol.cpp:3792
    10 xul.dll nsIMAPBodypart::GeneratePart(nsImapBodyShell*, bool, bool) mailnews/imap/src/nsImapBodyShell.cpp:409
    11 xul.dll nsIMAPBodypartLeaf::Generate(nsImapBodyShell*, bool, bool) mailnews/imap/src/nsImapBodyShell.cpp:528
  • bp-3e598d08-9130-4bad-b36d-5e12e0220905 91.13.0
    0 XUL nsImapServerResponseParser::msg_fetch_content(bool, int, char const*) mailnews/imap/src/nsImapServerResponseParser.cpp:1853
    1 XUL nsImapServerResponseParser::msg_fetch() mailnews/imap/src/nsImapServerResponseParser.cpp:1071
    2 XUL nsImapServerResponseParser::response_data() mailnews/imap/src/nsImapServerResponseParser.cpp:659
    3 XUL nsImapServerResponseParser::ParseIMAPServerResponse(char const*, bool, char*) mailnews/imap/src/nsImapServerResponseParser.cpp:189
    4 XUL nsImapProtocol::FetchMessage(nsTString<char> const&, nsIMAPeFetchFields, char const*, unsigned int, unsigned int, char*) mailnews/imap/src/nsImapProtocol.cpp:3742
    5 XUL nsImapProtocol::FetchTryChunking(nsTString<char> const&, nsIMAPeFetchFields, bool, char*, unsigned int, bool) mailnews/imap/src/nsImapProtocol.cpp:3774
    6 XUL nsImapProtocol::FallbackToFetchWholeMsg(nsTString<char> const&, unsigned int) mailnews/imap/src/nsImapProtocol.cpp:3504
    7 XUL nsImapBodyShell::Generate(char*) mailnews/imap/src/nsImapBodyShell.cpp:188
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: