Closed
Bug 1580841
Opened 6 years ago
Closed 6 years ago
Crash in [@ JS::ReadableStreamUpdateDataAvailableFromSource]
Categories
(Core :: DOM: Core & HTML, defect, P2)
Tracking
()
RESOLVED
DUPLICATE
of bug 1571037
| Tracking | Status | |
|---|---|---|
| firefox69 | --- | affected |
People
(Reporter: marcia, Unassigned)
Details
(Keywords: crash, regression)
Crash Data
This bug is for crash report bp-6e4420a7-f6b0-483d-804b-2ba060190911.
See while looking at release crashes - these macOS crashes seen to be visible in 69, but not in previous releases: https://bit.ly/2kdr8j9. All versions of macOS are affected. There is no moz crash reason for the crash.
Comments are not useful. Some code was touched in Bug 1559370
Some correlations:
(72.86% in signature vs 03.51% overall) Addon "amazondotcn@search.mozilla.org" = true
(69.29% in signature vs 01.97% overall) Module "APFS" = true
(68.57% in signature vs 02.84% overall) Addon "China Edition Addons Manager" = true
Top 10 frames of crashing thread:
0 XUL JS::ReadableStreamUpdateDataAvailableFromSource js/src/builtin/Stream.cpp:4673
1 libnss3.dylib PR_ExitMonitor nsprpub/pr/src/pthreads/ptsynch.c:646
2 XUL mozilla::dom::BodyStream::OnInputStreamReady dom/base/BodyStream.cpp:375
3 XUL XUL@0x8698af
4 XUL nsInputStreamReadyEvent::Run xpcom/io/nsStreamUtils.cpp:91
5 XUL mozilla::SchedulerGroup::Runnable::Run xpcom/threads/SchedulerGroup.cpp:295
6 libmozglue.dylib mozilla::detail::MutexImpl::unlock mozglue/misc/Mutex_posix.cpp:185
7 XUL mozilla::ThreadEventQueue<mozilla::PrioritizedEventQueue>::GetEvent xpcom/threads/ThreadEventQueue.cpp:157
8 XUL <name omitted> xpcom/threads/SchedulerGroup.cpp
9 XUL nsThread::GetPerformanceCounter xpcom/threads/nsThread.cpp:1020
Comment 1•6 years ago
|
||
:baku/:jorendorff may shed some light here.
Flags: needinfo?(jorendorff)
Flags: needinfo?(amarchesini)
Priority: -- → P2
Updated•6 years ago
|
Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(amarchesini)
Resolution: --- → DUPLICATE
Updated•6 years ago
|
Flags: needinfo?(jorendorff)
You need to log in
before you can comment on or make changes to this bug.
Description
•