Closed Bug 1516380 Opened 7 years ago Closed 6 years ago

Crash in mozilla::net::nsSocketEvent::Run

Categories

(Core :: Networking, defect, P3)

Product:
Core
Component:
Networking
Version:
64 Branch
Platform:
Unspecified
macOS
Type:
defect

Tracking

()

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
firefox-esr60 --- unaffected
firefox64 --- wontfix
firefox65 --- wontfix
firefox66 --- ?

People

(Reporter: timdream, Unassigned)

Details

(Keywords: crash, regression)

Crash Data

This bug was filed from the Socorro interface and is report bp-216382f7-448f-4d09-a987-101ce0181226. ============================================================= Top 10 frames of crashing thread: 0 @0x1104978e62 1 XUL mozilla::net::nsSocketEvent::Run netwerk/base/nsSocketTransport2.cpp 2 libmozglue.dylib arena_t::DallocSmall memory/build/mozjemalloc.cpp:3444 3 libmozglue.dylib BaseAllocator::free memory/build/mozjemalloc.cpp:3532 4 libmozglue.dylib free memory/build/malloc_decls.h:40 5 XUL mozilla::Runnable::Release xpcom/threads/nsThreadUtils.cpp:47 6 XUL nsThread::ProcessNextEvent xpcom/base/nsCOMPtr.h:371 7 XUL mozilla::ThreadEventQueue<mozilla::EventQueue>::PutEventInternal xpcom/threads/Queue.h:39 8 XUL <name omitted> xpcom/threads/ThreadEventTarget.cpp:183 9 libmozglue.dylib mozilla::detail::MutexImpl::lock mozglue/misc/Mutex_posix.cpp:132 =============================================================
Very low volume crash - only 3 crashes on 64 and on in 65.0b6.
status-firefox64: --- → affected
status-firefox65: --- → affected
Version: 59 Branch → 64 Branch
It's not clear to me what the reason of the crash is. Reports which have mozilla::Runnable::Release() on the stack seem to be wrong and the crash doesn't happen in nsSocketEvent::Run(). The others are strange too because mTransport cannot be null, so probably pointer to the event is wrong? Dragana, do you have any idea?
Flags: needinfo?(dd.mozilla)
I also checked and there are no URLs or comments in the few crash reports we have.
My Firefox has been crashy for quite some time, this is just one of the crash report it managed to send. These are other ones. https://crash-stats.mozilla.com/report/index/21dd20d1-d713-4f9b-a77c-b32ee0181230 https://crash-stats.mozilla.com/report/index/a0164e48-438e-4029-a6a2-40ebf0181228 https://crash-stats.mozilla.com/report/index/18a67f35-94ac-4b84-ba20-e6e3a0181227 https://crash-stats.mozilla.com/report/index/fc27a8a5-c168-4114-ba2e-3fe6b0181226 I don't really think it's really network related. All the stacks look like contain functions like "arena_t::DallocSmall" or "BaseAllocator::free". It is unclear to me why this happens even after downgrading from Beta to Release and even upgrading macOS to Mojave. It also suffers from occasional connection timeouts. Sometimes I can fix it by switching on/off offline mode, sometimes I would have to restart Firefox. I ran Apple Diagnostics on the machine and it didn't reveal anything. https://support.apple.com/en-us/HT202731 Is there anything else I should have look into?

My understanding is we're not going to have another 64 dot release given the impending 65 release.

status-firefox64: affected → wontfix
status-firefox66: --- → ?

This crash is very low volume, and the cause is not obvious. It could be bad memory. Low priority, sorry Tim.

Priority: -- → P3

This isn't happening for any current version in the last 6 months
https://crash-stats.mozilla.org/signature/?signature=mozilla%3A%3Anet%3A%3AnsSocketEvent%3A%3ARun&date=%3E%3D2019-08-23T14%3A17%3A00.000Z&date=%3C2020-02-23T14%3A17%3A00.000Z

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
Flags: needinfo?(dd.mozilla)
You need to log in before you can comment on or make changes to this bug.