Crash in [@ mozilla::MozPromise<T>::ThenValue<T>::DoResolveOrRejectInternal]
Categories
(Core :: WebRTC: Audio/Video, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr68 | --- | unaffected |
firefox70 | --- | unaffected |
firefox71 | + | fixed |
firefox72 | --- | fixed |
People
(Reporter: pascalc, Assigned: pehrsons)
References
(Depends on 1 open bug, Regression)
Details
(Keywords: crash, regression)
Crash Data
Attachments
(1 file)
47 bytes,
text/x-phabricator-request
|
pascalc
:
approval-mozilla-beta+
|
Details | Review |
This bug is for crash report bp-d0643524-ac33-4b00-ace0-7b02b0191018.
Top 10 frames of crashing thread:
0 xul.dll void mozilla::MozPromise<RefPtr<mozilla::media::Refcountable<nsTArray<RefPtr<mozilla::MediaDevice> > > >, RefPtr<mozilla::MediaMgrError>, 1>::ThenValue<`lambda at z:/task_1571393270/build/src/dom/media/MediaDevices.cpp:137:11', `lambda at z:/task_1571393270/build/src/dom/media/MediaDevices.cpp:166:11'>::DoResolveOrRejectInternal xpcom/threads/MozPromise.h
1 xul.dll nsresult mozilla::MozPromise<RefPtr<AudioDeviceInfo>, nsresult, 1>::ThenValueBase::ResolveOrRejectRunnable::Run xpcom/threads/MozPromise.h:402
2 xul.dll nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1225
3 xul.dll NS_ProcessNextEvent xpcom/threads/nsThreadUtils.cpp:486
4 xul.dll mozilla::ipc::MessagePump::Run ipc/glue/MessagePump.cpp:88
5 xul.dll MessageLoop::RunHandler ipc/chromium/src/base/message_loop.cc:308
6 xul.dll MessageLoop::Run ipc/chromium/src/base/message_loop.cc:290
7 xul.dll nsBaseAppShell::Run widget/nsBaseAppShell.cpp:137
8 xul.dll nsAppShell::Run widget/windows/nsAppShell.cpp:406
9 xul.dll XRE_RunAppShell toolkit/xre/nsEmbedFunctions.cpp:934
Reporter | ||
Comment 1•5 years ago
|
||
Tracking, this is a significant spike in crashes that happened in the last days and we will most likely want to uplift a fix to 71 beta. Crashes started in buildid 20191017215425, here is the changelog for this build: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=273c3db836e1a2ffdb7ce46d28d85adbbf2b70ba&tochange=c260b3893967535faf023573fdd429fc48738778
Comment 2•5 years ago
|
||
I think this is the same as bug 1589686, failing a diagnostic assert added in bug 1397528
Updated•5 years ago
|
Assignee | ||
Comment 4•5 years ago
|
||
Thanks for filing. This reveals a latent bug in our enumeration code, because by spec we're not supposed to reject in that path; except we've decided it's fine to reject if we have navigated away and the window is gone. For these failed assertions the window is not gone yet, so it's unclear why we're hitting them.
Bug 1397528 didn't cause this so I'll be removing the assert and file a followup for looking into this.
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 5•5 years ago
|
||
Pushed by pehrsons@gmail.com: https://hg.mozilla.org/integration/autoland/rev/a0b6647eea52 Remove recent assert that gets triggered by latent bug. r=jib
Updated•5 years ago
|
Assignee | ||
Comment 7•5 years ago
|
||
Comment on attachment 9102967 [details]
Bug 1589854 - Remove recent assert that gets triggered by latent bug. r?jib
Beta/Release Uplift Approval Request
- User impact if declined: A diagnostic assert may fail, this is not affecting beta directly, but dev edition will appear to crash. We haven't seen this happen in automation, but it does in the wild. No STR is known. Crash-stats can be used to verify this.
- Is this code covered by automated tests?: No
- Has the fix been verified in Nightly?: No
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): Trivial.
- String changes made/needed:
Reporter | ||
Comment 8•5 years ago
|
||
Comment on attachment 9102967 [details]
Bug 1589854 - Remove recent assert that gets triggered by latent bug. r?jib
Aproved for 71 beta, thanks
Comment 9•5 years ago
|
||
bugherder uplift |
Comment 10•5 years ago
|
||
bugherder |
Updated•5 years ago
|
Updated•2 years ago
|
Description
•