Make nsNetworkLinkService::calculateNetworkIdWithDelay shutdown aware
Categories
(Core :: Networking, task, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox130 | --- | fixed |
People
(Reporter: jstutte, Assigned: kershaw)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged])
Attachments
(1 file)
6dd015ad-8cf8-4cd1-8003-f28ff0240710 a StreamTrans thread is stuck inside the nsNetworkLinkService in calculateNetworkIdInternal. There could be a chance that by the time that the runnable executes the network has gone away for system shutdown and we are waiting for some looong timeout from the system?
| Reporter | ||
Updated•1 year ago
|
| Reporter | ||
Comment 1•1 year ago
|
||
It might help to just add a AppShutdown::IsInOrBeyond check right at the beginning of calculateNetworkIdWithDelay. It is not 100% clear to me, which would be an appropriate phase, maybe AppShutdownNetTeardown ?
| Assignee | ||
Comment 2•1 year ago
•
|
||
(In reply to Jens Stutte [:jstutte] from comment #1)
It might help to just add a
AppShutdown::IsInOrBeyondcheck right at the beginning ofcalculateNetworkIdWithDelay. It is not 100% clear to me, which would be an appropriate phase, maybeAppShutdownNetTeardown?
Thanks for filing this bug.
Yes, AppShutdownNetTeardown sounds correct to me. I'll submit a patch soon.
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Comment 3•1 year ago
|
||
Updated•1 year ago
|
Comment 5•1 year ago
|
||
| bugherder | ||
Description
•