Closed Bug 1689404 Opened 3 years ago Closed 3 years ago

Crash in [@ mozilla::detail::ProxyFunctionRunnable<T>::Run]

Categories

(Core :: Audio/Video: Playback, defect)

x86
Windows 7
defect

Tracking

()

RESOLVED FIXED
87 Branch
Tracking Status
firefox-esr78 --- unaffected
firefox85 --- unaffected
firefox86 --- unaffected
firefox87 + fixed

People

(Reporter: pascalc, Assigned: emmamalysz)

References

(Regression)

Details

(Keywords: crash, regression)

Crash Data

Attachments

(1 obsolete file)

Crash report: https://crash-stats.mozilla.org/report/index/4fa5885f-d746-413f-81bb-31cb00210128

Reason: EXCEPTION_ACCESS_VIOLATION_READ

Top 10 frames of crashing thread:

0 xul.dll mozilla::detail::ProxyFunctionRunnable<`lambda at /builds/worker/checkouts/gecko/dom/system/IOUtils.cpp:172:36', mozilla::MozPromise<mozilla::Ok, mozilla::dom::IOUtils::IOError, 1> >::Run xpcom/threads/MozPromise.h:1645
1 xul.dll mozilla::TaskQueue::Runner::Run xpcom/threads/TaskQueue.cpp:158
2 xul.dll nsThreadPool::Run xpcom/threads/nsThreadPool.cpp:302
3 xul.dll nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1165
4 xul.dll mozilla::ipc::MessagePumpForNonMainThreads::Run ipc/glue/MessagePump.cpp:302
5 xul.dll MessageLoop::RunHandler ipc/chromium/src/base/message_loop.cc:328
6 xul.dll MessageLoop::Run ipc/chromium/src/base/message_loop.cc:310
7 xul.dll static nsThread::ThreadFunc xpcom/threads/nsThread.cpp:404
8 nss3.dll _PR_NativeRunThread nsprpub/pr/src/threads/combined/pruthr.c:399
9 nss3.dll pr_root nsprpub/pr/src/md/windows/w95thred.c:139

Emma: Could this frequent Nightly crasher be from bug 1649611?
Nick: Could this be related to the changes in bug 1667276 etc.?

Changelog is https://hg.mozilla.org/mozilla-central/pushloghtml?changeset=37557864a6845bb8068904e44e8a7dd16746d211

Flags: needinfo?(nalexander)
Flags: needinfo?(emalysz)

(In reply to Sebastian Hengst [:aryx] (needinfo on intermittent or backout) from comment #1)

Nick: Could this be related to the changes in bug 1667276 etc.?

It is, of course, possible, but it seems very unlikely. The background task changes do impact the startup flow but (modulo errors) only when --backgroundtask ... is specfied on the command line, and certainly not in a way that's likely to interact with XPCOM threading.

Flags: needinfo?(nalexander)

I see a reference to IOUtils in the crash thread, so I think it's far more likely that my patch in bug 1649611 caused this.
I'll investigate more

Regressed by: 1649611
Has Regression Range: --- → yes
Assignee: nobody → emalysz
Status: NEW → ASSIGNED
Attachment #9199940 - Attachment is obsolete: true

[Tracking Requested - why for this release]: High volume on Nightly

Regressor was backed out from central: https://hg.mozilla.org/mozilla-central/rev/3bdf0c33844f1dc4198f0c44f1ff137b966cdc1d
New nightlies incoming.

Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Flags: needinfo?(emalysz)
Keywords: regression
Resolution: --- → FIXED
Target Milestone: --- → 87 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: