1810527 - Crash in [@ mozilla::MozPromiseRequestHolder<T>::Track]

Status: RESOLVED DUPLICATE of bug 1806490

(Core :: DOM: File, defect)

Description

[Gabriele Svelto [:gsvelto]]

Crash report: https://crash-stats.mozilla.org/report/index/9f163656-6c63-4fdb-b38e-f80190230116

MOZ_CRASH Reason: MOZ_DIAGNOSTIC_ASSERT(!Exists())

Top 10 frames of crashing thread:

0  libxul.so  mozilla::MozPromiseRequestHolder<mozilla::MozPromise<bool, nsresult, false> >::Track  xpcom/threads/MozPromise.h:1485
0  libxul.so  mozilla::MozPromise<bool, nsresult, false>::ThenCommand<mozilla::MozPromise<bool, nsresult, false>::ThenValue<mozilla::dom::FileSystemManager::BeginRequest  xpcom/threads/MozPromise.h:1016
0  libxul.so  mozilla::dom::FileSystemManager::BeginRequest  dom/fs/api/FileSystemManager.cpp:96
1  libxul.so  mozilla::dom::fs::FileSystemRequestHandler::GetRootHandle  dom/fs/child/FileSystemRequestHandler.cpp:344
2  libxul.so  mozilla::dom::FileSystemManager::GetDirectory  dom/fs/api/FileSystemManager.cpp:109
3  libxul.so  mozilla::dom::StorageManager::GetDirectory  dom/quota/StorageManager.cpp:805
4  libxul.so  mozilla::dom::StorageManager_Binding::getDirectory  dom/bindings/StorageManagerBinding.cpp:310
4  libxul.so  mozilla::dom::StorageManager_Binding::getDirectory_promiseWrapper  dom/bindings/StorageManagerBinding.cpp:326
5  libxul.so  mozilla::dom::binding_detail::GenericMethod<mozilla::dom::binding_detail::NormalThisPolicy, mozilla::dom::binding_detail::ConvertExceptionsToPromises>  dom/bindings/BindingUtils.cpp:3308
6  libxul.so  CallJSNative  js/src/vm/Interpreter.cpp:459

Windows and Linux has slightly different stacks but the problem is the same. We should cleanup this signature by removing the MozPromize frames so that the place where the problem takes place can bubble up.

Comment 1

[Jan Varga [:janv]]

This is probably bug 1806490.

Comment 2

[Andrew Sutherland [:asuth] (he/him)]

(In reply to Jan Varga [:janv] from comment #1)

This is probably bug 1806490.

Accordingly duping to bug 1806490; I can confirm this crash came from a build that pre-dates the landing of the fix.