Closed Bug 1907539 Opened 1 year ago Closed 1 year ago

Make nsNetworkLinkService::calculateNetworkIdWithDelay shutdown aware

Categories

(Core :: Networking, task, P2)

Unspecified
macOS
task

Tracking

()

RESOLVED FIXED
130 Branch
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?

OS: Unspecified → macOS
See Also: → 1584165

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 ?

Flags: needinfo?(kershaw)

(In reply to Jens Stutte [:jstutte] from comment #1)

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 ?

Thanks for filing this bug.
Yes, AppShutdownNetTeardown sounds correct to me. I'll submit a patch soon.

Flags: needinfo?(kershaw)
Severity: -- → N/A
Priority: -- → P2
Whiteboard: [necko-triaged]
Assignee: nobody → kershaw
Status: NEW → ASSIGNED
Pushed by kjang@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/c5c3f0f3c83d Don't calculate network ID during shutdown, r=acreskey
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 130 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: