pages and I didn’t bother to save/name that doc (.pages) because I was using it as a place holder of info while I worked/researched other sites (thus multiple tabs opened in Safari). pages - I did a simple cut/paste from an email into. Although I did have something similar happen while using Apple’s. I will continue to monitor this situation with using just Safari. I was fully aware that I was walking into the M1 scene upon purchase and knew that there would be some sort of kinks to be worked out (ala Rosetta).
If you left the Jetpack connection active I think you'll see it won't encounter this. But I would wait until you see what Safari shows you as well as how a constant connection reacts.Īs others encountering the issue, I doubt many people are holding pages open like you with a severed connection. All you can do is post a bug report with FireFox and Apple so they are aware of the issue.
Sadly, you are a trailblazer! So issues like this can be a pain in the butt for you. Here's more on Rosetta 2 which does the translation Rosetta2 It's not perfect! But its quite good! Here we are pushing things as web based applications like FireFox are more complex so it's possible it just won't work as you expected.
FIREFOX FOR MAC M1 CODE
Sorry I guess I wasn't too clear, the issue is on how web sites work so if you break the connection to their server the page expires! I fear this is the root issue here.Īs far the version of macOS the issue you are locked in to the M Series SoC versions Big Sur and Monterey, I don't see that in its self is the issue this gets into translation running Intel code on an Arm based system (M Series SoC). I would test with a dedicated wired connection but that is not possible at the moment.īy - Here's a bit more on Extended Support version of fireFox You shouldn't need this version its not really the version of personal use. So, now I am testing this random-shutdown by just using Safari but if you can give any further direction, that would be helpful. I cannot believe that I’m the only person with an M1 MBP using Firefox and having this issue. Ridiculous.Īll Apple can tell me is to go after 3-party apps (okay… Firefox…) and use Safari. I’m just peeved that I’ve spent nearly $2k on this MBP (after upgrades, etc.) and this is what I get. I’ve reinstalled Firefox while on one of the tech support calls with Apple (few months ago) and as I’ve said, FF auto-updates. When you say there may be an OS level or an app issue, what are you exactly referring to? Reinstalling Monterey? I noticed the random shut-downs while in Big Sur and it got progressively worse in Monterey - when I say progressively worse - something like Firefox completely shutting down (offline) a couple of times a week. And yes, the WiFi jetpack (major US carrier) may not be up to M1 standards, I agree.
Not sure what you are referring to wrt “Extended Support 91.4.1esr…”. My Firefox is up-to-date (95.0.2) as is macOS Monterey. Apple's other answer is for me to use Safari.Īnyone else have this issue or have any clue as to what's going on? A lot of money spent on this MBP just so I can have constant and no-patterned closures. This spontaneous Firefox closing issue has happened in both Big Sur and Monterey. I have never had this problem until this 2020 MBP (M1) - my previous MBP was a 2010. Many times after I have awakened the MBP in order to re-connect to wifi and continue reading tabs (mostly articles) that I've opened, I have found that Firefox and all of those tabs have closed - again, while disconnected from the Jetpack/Wifi.Īpple tells me it is a Firefox issue and to contact Firefox. Because I use a jetpack which has usage limits, I will disconnect from the jetpack/wifi when I'm not using it but will leave existing tabs opened in Firefox and put the MBP to sleep. I use Firefox as my go-to browser and will have opened a number of tabs at any given time. MBP 2020 (M1) - I use a jetpack to connect to the internet.
0 kommentar(er)
