Bug 41801: Fix handleProcessReady in TorSettings.init

Merge Info

Related Issues

• #41801 (closed)

Backport Timeline

• Immediate - patchsets for critical bug fixes or other major blocker (e.g. fixes for a 0-day exploit) OR patchsets with trivial changes which do not need testing (e.g. fixes for typos or fixes easily verified in a local developer build)
• Next Minor Stable Release - patchset that needs to be verified in nightly before backport
• Eventually - patchset that needs to be verified in alpha before backport
• No Backport - patchset for the next major stable

Upstream Merging

• Merge to base-browser - typically for !fixups to patches in the base-browser branch, though sometimes new patches as well
  • NOTE: if your changeset includes patches to both base-browser and tor-browser please please make separate merge requests for each part

Issue Tracking

• Link resolved issues with appropriate Release Prep issue for changelog generation

Change Description

When moving code in 2df6696d, I missed this error. I think it's a hard condition to happen, but still, handling this possible race condition in the correct way is a good idea.

I will rebase to 102.12, but still created this MR since I wanted to copy this fixup also to TB 115 😅.

Also, it seems a pretty simple change that we could backport already. But we also haven't received any error relatable to it either, so we could also wait/no backport it at all.