Closed
Bug 1673182
Opened 4 years ago
Closed 4 years ago
Crash in [@ mapped_hyph::ffi::mapped_hyph_is_valid_hyphenator]
Categories
(Core :: Layout: Text and Fonts, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1672388
People
(Reporter: sefeng, Unassigned)
Details
(Keywords: crash)
Crash Data
Crash report: https://crash-stats.mozilla.org/report/index/143aae9c-e995-4e49-8c59-613ef0201016
Reason: EXCEPTION_ACCESS_VIOLATION_READ
Top 10 frames of crashing thread:
0 xul.dll mapped_hyph::ffi::mapped_hyph_is_valid_hyphenator third_party/rust/mapped_hyph/src/ffi.rs:169
1 xul.dll nsHyphenator::nsHyphenator intl/hyphenation/glue/nsHyphenator.cpp:260
2 xul.dll nsHyphenationManager::GetHyphenator intl/hyphenation/glue/nsHyphenationManager.cpp:149
3 xul.dll nsHyphenationManager::ShareHyphDictToProcess intl/hyphenation/glue/nsHyphenationManager.cpp:349
4 xul.dll mozilla::dom::ContentParent::RecvGetHyphDict dom/ipc/ContentParent.cpp:5449
5 xul.dll mozilla::dom::PContentParent::OnMessageReceived ipc/ipdl/PContentParent.cpp:15631
6 xul.dll mozilla::ipc::MessageChannel::DispatchMessage ipc/glue/MessageChannel.cpp:2070
7 xul.dll mozilla::ipc::MessageChannel::MessageTask::Run ipc/glue/MessageChannel.cpp:1953
8 xul.dll mozilla::TaskController::DoExecuteNextTaskOnlyMainThreadInternal xpcom/threads/TaskController.cpp:515
9 xul.dll mozilla::detail::RunnableFunction<`lambda at /builds/worker/checkouts/gecko/xpcom/threads/TaskController.cpp:85:7'>::Run xpcom/threads/nsThreadUtils.h:577
This is a new signature that is introduced recently. All crashes occur on Windows 10. Although the crashes happened in a third-party library, I still filed it because of multiple crashes from various installations with a similar call stack.
Reporter | ||
Comment 1•4 years ago
|
||
Looks like it's a duplicate of bug 1672388. However, I don't have access to that one so I can't mark this one as a duplicate of it.
I'll leave it open for now....
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Updated•4 years ago
|
Resolution: FIXED → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•