Bug? On MacOS with Firefox container tabs: SophosModernWebIntelligence spins

Hi Wayne.

Thanks for reaching out to the Sophos Community Forum. 

May I ask if the affected device is enrolled in the EAP group for MacOs devices? 

Yes.

Thanks for confirming. I've moved your post over to our EAP group for MacOS.

Please allow me some time to inquire with our team regarding your issue, and I will update you here.

Could you let me know if the issue occurs with any other Web Browsers or if this issue is specific to Firefox? Please also provide me with the version of Firefox you are using, so I may try to replicate this issue on my side. 

It's Firefox 129.0.2 (64-bit), which should be the latest. Running the Simple Tab Groups extension, which uses Firefox's Container Tabs. Also using the following extensions: 1Password, Facebook Container, Firefox Multi-Account Containers, and Zotero Connector.

I don't use Safari anymore because the Simple Tab Groups and taking advantage of Containers is just too valuable. (That is, a Container maintains cookies and all the other goodies, separate from other containers, so you can literally login to Google for work in one Container and Google for home in another Container and not have weird confusions between the two.

Sorry, don't have much more. It could have nothing to do with Firefox, like I said, but Firefox might be firing off separate processes for each tab or something like that. And it's in Firefox that I notice the problem because I'll click on four or five links (to open new tabs) and when I look back again, none of the tabs has actually updated -- they all have the Cylon dots moving back and forth.

To add some more information, this is with an Intel-based Macbook Pro.

Also, I sampled the process while it was spinning, if that would be helpful. And I noticed that it DID eventually resolve the tabs and didn't keep spinning. (I hadn't had the patience to wait long enough before, but this time I scrolled through the process sample and by the time I'd gotten to the end, the tabs had resolved.)

To add some more information, this is with an Intel-based Macbook Pro.

Also, I sampled the process while it was spinning, if that would be helpful. And I noticed that it DID eventually resolve the tabs and didn't keep spinning. (I hadn't had the patience to wait long enough before, but this time I scrolled through the process sample and by the time I'd gotten to the end, the tabs had resolved.)