Closed Bug 1774658 Opened 2 years ago Closed 2 years ago

Firefox becomes unresponsive when sharing my network connection after the latest KB5014699 update

Categories

(Core :: Networking, defect)

Firefox 101
x86_64
Windows 10
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: vangelis.xanthakis, Unassigned)

References

Details

Attachments

(1 file)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:101.0) Gecko/20100101 Firefox/101.0

Steps to reproduce:

Prerequisites

  • Windows 10 Pro - 21H2 - 19044.1766
  • Windows Feature Experience Pack 120.2212.4180.0
  • This issue happens after the recent KB5014699 update
  • Using HyperV with windows VM that shares the host computer network card

Steps

  • Keep firefox 101.0.1 (64-bit) open - multiple tabs to various web sites
  • Go to Windows Network and Internet Settings
  • Then click Change adapter options
  • Choose the WiFi adapter and open it (d-click)
  • Click Properties
  • Click Sharing
  • Check the "Allow other network users to connect ... etc."
  • Click OK

Actual results:

Firefox freezes and becomes unresponsive but it will become responsive after shuting down Firefox from the Windows Task Manager

Expected results:

Firefox working without issues.
Other notes:

  • Chrome is not affected by the above steps.
  • No other apps seem to be affected.

The Bugbug bot thinks this bug should belong to the 'Core::Networking' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Networking
Product: Firefox → Core

After a while I noticed that it happens when you are doing the change on the card adapter - then you restart firefox after the crash and it is working as expected. Not sure what is causing this behaviour, I will keep an eye on it.

Component: Networking → Security: Process Sandboxing

Latest update, I am afraid that the issue is not with firefox as it appears that other applications on my laptop are facing networking problems after the update. So when I turn on the network sharing of my host's wi-fi adapter it will then cause all sorts of networking problems to the applications running on the host. e.g. MS Outlook, now Chrome look that they cannot connect to network resources. So it doesn't look to be a firefox issue. The only thing to say for sure is that thse issues are noticed following the latest windows update. Please note that when the network is shared the VM works well but the problem is with the host's processes.

Okay this is the last comment, I uninstalled KB5014699 and all is back to normal. Obviously, Windows 10 will reinstall the update later on but i don't have any other option at the moment.

OS: Unspecified → Windows 10
Hardware: Unspecified → x86_64

That is on Windows 11 - mine is Windows 10 Pro and the following confirms the issue https://www.ghacks.net/2022/06/18/windows-june-2022-updates-break-wi-fi-hotspot-feature-microsoft-services-on-arm/

Component: Networking → Security: Process Sandboxing

Ed, there doesn't seem to be anything in the comments or description that even hints at Sandboxing, so was this move made in error?

Component: Security: Process Sandboxing → Networking
Flags: needinfo?(eguloien)

Kershaw, you recommended this might be a fitting component to assign to, can you assist?

Flags: needinfo?(eguloien) → needinfo?(kershaw)

Hi Reporter,

Could you see this instruction and try to crash Firefox?
With the crash report, we can understand why Firefox hangs.

Thanks.

Flags: needinfo?(kershaw) → needinfo?(vangelis.xanthakis)

Another easier approach could be trying to create a process dump from windows task manager.
Thanks.

If you read the previous comments, this is not a Firefox as I initially thought but an issue with Windows updates as reported above. Thanks.

Flags: needinfo?(vangelis.xanthakis)

I'd close this for now. Feel free to reopen if you think this is a Firefox issue.

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
See Also: → 1774783
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: