Closed Bug 1664858 Opened 5 years ago Closed 5 years ago

version 78 Crash in [@ MsgHdrsToTArray]

Categories

(MailNews Core :: Networking: IMAP, defect)

x86
Windows 10
defect

Tracking

(thunderbird_esr78+ fixed, thunderbird81 affected)

RESOLVED FIXED
82 Branch
Tracking Status
thunderbird_esr78 + fixed
thunderbird81 --- affected

People

(Reporter: wsmwk, Assigned: mkmelin)

References

(Regression)

Details

(Keywords: crash, regression)

Crash Data

Attachments

(1 file)

Our imap threading friend?

Crash report: https://crash-stats.mozilla.org/report/index/0264f555-6cb5-449f-9eaf-a7c040200914

Top 10 frames of crashing thread:

0 xul.dll MsgHdrsToTArray comm/mailnews/base/src/nsMsgUtils.cpp:1886
1 xul.dll nsImapMailFolder::OnStopRunningUrl comm/mailnews/imap/src/nsImapMailFolder.cpp:4939
2 xul.dll nsMsgMailNewsUrl::SetUrlState comm/mailnews/base/src/nsMsgMailNewsUrl.cpp:231
3 xul.dll nsImapMailFolder::SetUrlState comm/mailnews/imap/src/nsImapMailFolder.cpp:6337
4 xul.dll `anonymous namespace'::SyncRunnable5<nsIImapMailFolderSink, nsIImapProtocol*, nsIMsgMailNewsUrl*, bool, bool, nsresult>::Run comm/mailnews/imap/src/nsSyncRunnableHelpers.cpp:221
5 xul.dll nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1211
6 xul.dll NS_ProcessNextEvent xpcom/threads/nsThreadUtils.cpp:501
7 xul.dll mozilla::ipc::MessagePump::Run ipc/glue/MessagePump.cpp:109
8 xul.dll MessageLoop::RunHandler ipc/chromium/src/base/message_loop.cc:308
9 xul.dll MessageLoop::Run ipc/chromium/src/base/message_loop.cc:290

I wonder if this surfaced after bug 1658797.

Assignee: nobody → mkmelin+mozilla
Status: NEW → ASSIGNED
Attachment #9175705 - Flags: review?(benc)

(In reply to Magnus Melin [:mkmelin] from comment #2)

...
I wonder if this surfaced after bug 1658797.

I'd say both crashes started at the same time. Both first appear with 78.0b2 BETA - this bug with buildid 20200622204154 and bug 1658797 with buildid 20200616103211

So the regression is likely in the uplifts https://hg.mozilla.org/releases/comm-beta/pushloghtml?fromchange=THUNDERBIRD_78_0b1_RELEASE&tochange=THUNDERBIRD_78_0b2_RELEASE&full=1 If not that, then the merge for 78.0b1

Summary: Crash in [@ MsgHdrsToTArray] → version 78 Crash in [@ MsgHdrsToTArray]
Comment on attachment 9175705 [details] [diff] [review] bug1664858_msghdrstoarray.patch Review of attachment 9175705 [details] [diff] [review]: ----------------------------------------------------------------- Yes, looks like my fault, and your patch looks sound to me. Ideally, I'd like to go through and be really explicit about parameter validity in these sorts of cases (ie is it acceptable to pass in null? how about empty arrays?), but better to wait until the array-removal dust settles. The null-pointer problem tends go away with `nsTArray<>&` params, and I'd think empty arrays should perfectly valid (if a little pointless). I shall take great pleasure in finally removing `MsgHdrsToTArray()` and the like.
Attachment #9175705 - Flags: review?(benc) → review+

It will be interesting to see if this kills it dead

Target Milestone: --- → 82 Branch

Pushed by geoff@darktrojan.net:
https://hg.mozilla.org/comm-central/rev/250a6c111f71
fix Crash in [@ MsgHdrsToTArray]. r=benc DONTBUILD

Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Pushed by mkmelin@iki.fi: https://hg.mozilla.org/comm-central/rev/f51e43c76fbc followup - allow null messages arg to nsImapMailFolder::InitCopyState. rs=test-bustage-fix
Attachment #9175705 - Flags: approval-comm-esr78?

Comment on attachment 9175705 [details] [diff] [review]
bug1664858_msghdrstoarray.patch

[Triage Comment]
Approved for esr78

Attachment #9175705 - Flags: approval-comm-esr78? → approval-comm-esr78+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: