Closed Bug 1907691 Opened 1 year ago Closed 1 year ago

Crash in [@ strlen | nsCharTraits<T>::length] via nsImapServerResponseParser::mailbox and nsImapServerResponseParser::ParseIMAPServerResponse(

Categories

(Thunderbird :: General, defect)

Thunderbird 115
Unspecified
Windows 10
defect

Tracking

(thunderbird_esr115 affected, thunderbird_esr128+ wontfix, thunderbird131+ fixed)

RESOLVED FIXED
132 Branch
Tracking Status
thunderbird_esr115 --- affected
thunderbird_esr128 + wontfix
thunderbird131 + fixed

People

(Reporter: wsmwk, Assigned: mkmelin, NeedInfo)

References

(Blocks 1 open bug, Regression)

Details

(Keywords: crash, regression)

Crash Data

Attachments

(1 file)

Reporter of this crash indicates importing outlook data. states "Thunderbird updated, and now refuses to start, so I now have no access to my e-mail. "

Crash report: https://crash-stats.mozilla.org/report/index/cdaef368-8b27-470e-a5a9-4f2af0240711

Reason: EXCEPTION_ACCESS_VIOLATION_READ

Top 10 frames:

0  ucrtbase.dll  strlen
1  xul.dll  nsCharTraits<char>::length(char const*)  xpcom/string/nsCharTraits.h:423
1  xul.dll  nsTDependentString<char>::nsTDependentString(char const*)  xpcom/string/nsTDependentString.h:76
1  xul.dll  nsImapServerResponseParser::mailbox(nsImapMailboxSpec*)  mailnews/imap/src/nsImapServerResponseParser.cpp:788
2  xul.dll  nsImapServerResponseParser::mailbox_list(bool)  mailnews/imap/src/nsImapServerResponseParser.cpp:772
3  xul.dll  nsImapServerResponseParser::response_data()  mailnews/imap/src/nsImapServerResponseParser.cpp:447
4  xul.dll  nsImapServerResponseParser::ParseIMAPServerResponse(char const*, bool, char*)  mailnews/imap/src/nsImapServerResponseParser.cpp:189
5  xul.dll  nsImapProtocol::List(char const*, bool, bool)  mailnews/imap/src/nsImapProtocol.cpp:7676
6  xul.dll  nsImapProtocol::DiscoverMailboxList()  mailnews/imap/src/nsImapProtocol.cpp:7267
7  xul.dll  nsImapProtocol::ProcessAuthenticatedStateURL()  mailnews/imap/src/nsImapProtocol.cpp:7893
Flags: needinfo?(mkmelin+mozilla)
Blocks: tb128found

This isn't a new crash signature, but the stack might be new.

Severity: -- → S3
Summary: Crash in [@ strlen | nsCharTraits<T>::length] → Crash in [@ strlen | nsCharTraits<T>::length] via nsImapServerResponseParser::mailbox and nsImapServerResponseParser::ParseIMAPServerResponse(
Flags: needinfo?(mkmelin+mozilla)

A few users' crash comments state they only started crashing with version 128.
bp-63601022-3113-461e-9dff-6400a0240617 is using davmail and beta builds.
Crashes are often at startup

Flags: needinfo?(mkmelin+mozilla)
Version: Thunderbird 128 → Thunderbird 115
Assignee: nobody → mkmelin+mozilla
Status: NEW → ASSIGNED
Flags: needinfo?(mkmelin+mozilla)
Crash Signature: [@ strlen | nsCharTraits<T>::length] → [@ strlen | nsCharTraits<T>::length] [@ nsCharTraits<T>::length]
Attachment #9424619 - Attachment description: Bug 1907691 - Fix Crash in [@ strlen | nsCharTraits<T>::length] via nsImapServerResponseParser::mailbox and nsImapServerResponseParser::ParseIMAPServerResponse. r=#thunderbird-reviewers → Bug 1907691 - Fix Crash in [@ strlen | nsCharTraits<T>::length] via nsImapServerResponseParser::mailbox and nsImapServerResponseParser::ParseIMAPServerResponse. r=tobyp
Target Milestone: --- → 132 Branch

How would you feel about taking this to today's beta? Or, does it need a couple days on daily?

Flags: needinfo?(mkmelin+mozilla)

Any thoughts on a possible workaround, given that this often happens on startup?

It shouldn't be a problem but I would give it two days or so on daily.
I don't know exactly what would cause it.

Flags: needinfo?(mkmelin+mozilla)

Pushed by geoff@darktrojan.net:
https://hg.mozilla.org/comm-central/rev/5dbcfc60b279
Fix Crash in [@ strlen | nsCharTraits<T>::length] via nsImapServerResponseParser::mailbox and nsImapServerResponseParser::ParseIMAPServerResponse. r=tobyp

Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED

Comment on attachment 9424619 [details]
Bug 1907691 - Fix Crash in [@ strlen | nsCharTraits<T>::length] via nsImapServerResponseParser::mailbox and nsImapServerResponseParser::ParseIMAPServerResponse. r=tobyp

[Approval Request Comment]
User impact if declined: may crash
Testing completed (on c-c, etc.): c-c
Risk to taking this patch (and alternatives if risky): should be safe

Attachment #9424619 - Flags: approval-comm-esr128?
Attachment #9424619 - Flags: approval-comm-beta?

Comment on attachment 9424619 [details]
Bug 1907691 - Fix Crash in [@ strlen | nsCharTraits<T>::length] via nsImapServerResponseParser::mailbox and nsImapServerResponseParser::ParseIMAPServerResponse. r=tobyp

[Triage Comment]
Approved for beta

Attachment #9424619 - Flags: approval-comm-beta? → approval-comm-beta+

Comment on attachment 9424619 [details]
Bug 1907691 - Fix Crash in [@ strlen | nsCharTraits<T>::length] via nsImapServerResponseParser::mailbox and nsImapServerResponseParser::ParseIMAPServerResponse. r=tobyp

[Triage Comment]
Approved for esr128

Attachment #9424619 - Flags: approval-comm-esr128? → approval-comm-esr128+
Regressions: 1921739

I looks like this crash bug got introduced by bug 1907691, which uses nsDependentCString with a null string parameter.

The patch for bug 1853365 needs to get re-reviewed, to check for other places where nsDependentCString might get potentially used with a null pointer.

Keywords: regression
Regressed by: 1853365

Please back out https://hg.mozilla.org/releases/comm-esr128/rev/4f004e83ed9f from 128. We'll handle the rest in bug 1921739.

Flags: needinfo?(daniel)
Flags: needinfo?(daniel)

Comment on attachment 9424619 [details]
Bug 1907691 - Fix Crash in [@ strlen | nsCharTraits<T>::length] via nsImapServerResponseParser::mailbox and nsImapServerResponseParser::ParseIMAPServerResponse. r=tobyp

Removing approval flag per comments 15-16.

Attachment #9424619 - Flags: approval-comm-esr128+

Hello,

Are there any specific STR that QA could perform in order to reproduce the faulty behaviour(crash) on an affected build and properly verify and confirm that it is fixed?

Flags: needinfo?(kaie)
Blocks: 1954306
No longer blocks: 1954306
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: