Safari 14 on Big Sur: How to prevent a webpage from automatically reloading because it was using significant memory?

In previous versions of Safari, only a message banner would pop up informing me that a webpage was taking up significant memory. Under Safari 14, the browser now automatically reloads the webpage without my permission, and there seems to be no way to turn this function off.


I am unable to pause lectures, type notes in another app, and then return to play the recorded lecture without the webpage reloading, causing me to lose my place in the lecture. For my purposes, Safari has become unusable because of this new, automatic reloading. I preferred a message banner appearing on top of the webpage so I could reload at my convenience.


Is there a fix that I can do through Terminal to turn this function off? What can I do?

MacBook Pro 13″, macOS 11.0

Posted on Nov 14, 2020 4:15 PM

Reply
Question marked as Top-ranking reply

Posted on Mar 4, 2021 1:02 PM

I had the same problem when watching Disney+ I tried a few different things but finally seemed to have stopped it happening.

I monitored the memory use of the Disney+ tab in Activity monitor.


Under safari > Settings for this website - I turned off "Content Blockers"

I am running Ghostry Lite - so I "Trusted the site"

I am running AdBlock - so I added www.disneyplus.com to the sites allowed to show Ads.


If I do the above and play Disney+ in a separate window the memory usage fluctuates but doesn't grow like it used to. Previously I would get the warning when the tab used around 2.0GB memory. Now it stays between 650Mb-850Mb





Similar questions

198 replies

Jun 14, 2021 6:40 AM in response to pkabirr

Welcome, pkabirr, to Apple Support Communities!


The proper JavaScript solution to this issue is to use Server-side storage, rather than abusing the users’ resources.


In order to mitigate the nature of storing sensitive data on your server, I would recommend encryption.


Otherwise, a non-JavaScript, non-browser solution will likely be necessary (like a standalone App).

Jun 14, 2021 12:43 PM in response to Halliday

@Halliday,


Thank you for the response. Though, for completeness, we need to substitute "proper" in your answer to "what some of the developers consider solely appropriate, due to their belief in thin client applications only".


Unfortunately Microsoft does not give us any other modern framework for developing Microsoft Office add-ins, only a Javascript-based one, which runs in a Webview.


With our old COM-based add-in, "abusing resources" was never an issue with anyone from our clients. And they appreciated that we didn't store their data on our servers, whether encrypted or non-encrypted.


The memory restriction makes sense for >99% of the websites, I agree. However for the remaining 1%, we need to accept the niche and the reality of computationally and memory intensive Web applications, rather than imperatively flip the switch.


Which is why I think that a whitelist-based solution is not a bad one - our power users having huge Excel reports would be capable of setting it up on their end, and people with small reports will not need one in the first place.

Jun 14, 2021 8:02 PM in response to pkabirr

pkabirr wrote:

@Halliday,

Thank you for the response. Though, for completeness, we need to substitute "proper" in your answer to "what some of the developers consider solely appropriate, due to their belief in thin client applications only".

You sure are intent upon justifying your abuse of the resources of web-browser clients.


If you wish to go beyond that, simply create your own App that has all the resources afforded full Apps.


Unfortunately Microsoft does not give us any other modern framework for developing Microsoft Office add-ins, only a Javascript-based one, which runs in a Webview.

Take that up with Microsoft. Besides, you could create your own App based upon its own «Webview», which could allow whatever resource usage your App may choose.


With our old COM-based add-in, "abusing resources" was never an issue with anyone from our clients. And they appreciated that we didn't store their data on our servers, whether encrypted or non-encrypted.

More old tech, that is not an excuse for «”abusing resources"» belonging to other Apps.


The memory restriction makes sense for >99% of the websites, I agree. However for the remaining 1%, we need to accept the niche and the reality of computationally and memory intensive Web applications, rather than imperatively flip the switch.

This «switch» pertains to software that you have no control over.


Besides, the International Internet Standards governing Web communications already provides for the use of Server-side memory for such «niche» needs.


If that is insufficient, then, like I’ve already said, you can create your own App, even if it is written using its own «Webview».


Then, you’ll be free to impose your own resource rules!


Which is why I think that a whitelist-based solution is not a bad one - our power users having huge Excel reports would be capable of setting it up on their end, and people with small reports will not need one in the first place.

While I am not privy to the current International Internet Standards work, governing Web communications, I have seen enough to suggest that a revision in how Web-browsers (and other clients) may communicate with servers, in order to “negotiate” capabilities and resources, is “in the works”.


I’m reasonably certain that «a whitelist-based solution» is precisely the sort of “solution” they are working to avoid.


For one thing, using client or server “IDs” is too easily “spoofed”, and doesn’t scale well at all.

Jun 15, 2021 12:37 AM in response to Halliday

@Halliday,


I understand and respect your opinion on the matter.


On my end, I see no problem (and our clients didn't either) with computationally and memory intensive JS applications. Whether we like it or not, much of even desktop software (non-resource-constrained!) is written in JS / TypeScript nowadays.


In 2021, a browser tab is not really semantically different from a standalone application.

If one disagrees with a particular tab's resource usage, they can opt out using their legs (and CMD+W).


I was always absolutely OK with a guided warning (Ideally in the format of "We see that this tab here is using a lot of memory which can take resources from other apps and make your Mac less responsive. Do you want to shut it down, or do you want us not to ask about it again?")


At the same time, a force shutdown without asking is so Joseph Stalin.


On my end, I hold an opinion that at all times the user should stay in control of their resource allocation. What Apple did with this update is take that away from the users. Any sort of "food stamp style" RAM caps risk throwing out a baby with the bathwater.


This whole thread with over 1.5k upvotes is a proof of how both people and application developers are unhappy with this move, and no amount of Kool-Aid is going to fix this.

Jun 18, 2021 12:20 AM in response to Halliday

@Halliday , I am glad to see a spark of understanding in your last message.


I wish to point out one important observation though: you keep repeating the word "abuse" in your answers. It is a highly subjective term - and I still hold the position that it's the end user who must decide whether something is an abuse or not.


Similarly, I am not a holy warrior and I don't really wish to "impose my desires" on anyone - what I felt was right to do was to point out that it was Apple who did the imposing this time, and I did my best to explain why this is wrong. It was a kind request on my end, and it's up to the decision makers to decide now.


Also, as an observation, you might disagree with me on the point of Web apps becoming not really different from desktop apps - I definitely feel this has been the trend in the last years, for better or worse. That might be a crucial difference in our positions.


I will leave this discussion now and I thank you for the dialogue.


Any Apple decision makers that matter probably don't monitor the user space anyway - and I already gave my feedback to them directly. On the other hand, most of who read this thread don't care a bit about what I do and will probably join your position. ****, even I am mostly aligned with it for non-business web applications and consumer-facing websites.


Now, back to writing my monstrous, resource-abusing software![*]


[*] as I pointed out, relatively high memory usage only happens for a handful of high-profile clients with enormously sized reports. It's not a problem for most of our users.


Jun 18, 2021 2:07 PM in response to pkabirr

pkabirr wrote:

@Halliday , I am glad to see a spark of understanding in your last message.

I wish to point out one important observation though: you keep repeating the word "abuse" in your answers. It is a highly subjective term - and I still hold the position that it's the end user who must decide whether something is an abuse or not.

Actually, it is «abuse» of resources of software you do not have any semblance of control over.


It is «abuse» of resources that the International Internet Standards, that pertain to World-Wide Web (WWW) interactions, have not given over to control by websites.


Hence, it is not about resources the Web-Browsers need yield control over to websites or even users.


However. If you, and/or your users, wish to petition Apple for control of such resources, you will get nowhere, here, on these fora.


Instead, you, and your users, are completely free to petition Apple for such through their provided Feedback mechanisms: Product Feedback - Apple.


Note: I am but a fellow user. I have no special relationship with Apple or Apple’s developers.


Similarly, I am not a holy warrior and I don't really wish to "impose my desires" on anyone - what I felt was right to do was to point out that it was Apple who did the imposing this time, and I did my best to explain why this is wrong. It was a kind request on my end, and it's up to the decision makers to decide now.

Both Apple and other Web-Browser companies have been imposing these limitations for as long as there has been a WWW.


It is nothing new, nor a feature of any single company.


(Of course, different Web-Browsers are completely free to impose different limitations. It is the wide variation in such limitations, and the need for websites to properly negotiate such, that is the root cause in the changes in International Internet Standards, governing the WWW, that I have written of, in earlier comments.)


Also, as an observation, you might disagree with me on the point of Web apps becoming not really different from desktop apps - I definitely feel this has been the trend in the last years, for better or worse. That might be a crucial difference in our positions.

While it, undoubtedly, is a contributing factor, in motivations, it is, however, basically, irrelevant.


It is one things to write you own Apps with their own resource requirements.


It is, fundamentally, a distinct proposition to insist upon using the resources of an App that you have no control over.


I will leave this discussion now and I thank you for the dialogue.

Any Apple decision makers that matter probably don't monitor the user space anyway - and I already gave my feedback to them directly. On the other hand, most of who read this thread don't care a bit about what I do and will probably join your position. ****, even I am mostly aligned with it for non-business web applications and consumer-facing websites.

(Emphasis added)


Good.


If you feel that way about other software, then why don’t you respect the same for others?


Simply do as I have recommended: create your own App (potentially built upon a Webview) so you have full control of the resources involved, rather than insisting that someone else modify their App (a web-browser) to accommodate your resource use desires.


Now, back to writing my monstrous, resource-abusing software![*]

[*] as I pointed out, relatively high memory usage only happens for a handful of high-profile clients with enormously sized reports. It's not a problem for most of our users.

Then, so long as you don’t do as I have recommended, so you have control over the resources involved, those users will be disadvantaged by your refusal to “do the right thing”™️.


The solution is entirely in your hands, if you choose to avail yourself of such.


You need not depend upon any other App developers.

Jul 9, 2021 10:24 AM in response to LemonsterOG

Welcome, LemonsterOG, to Apple Support Communities!


I, too, have had some trouble with Disney+, but got no warning message/dialogue, but the video continued (under a new process) just a little before where it quit.


I was using Safari under Big Sur, on an Intel based Mac mini.


With the same setup, I had no such problem with Netflix.


(I only used the websites for this testing. For myself and my family, I always use the Apps, never the websites.)


Unfortunately, the problem is with the website, not the Browser or Operating System (OS), or hardware.


The most appropriate place to complain is with the website owner.


In the meantime, you may have a different experience with different Browsers.

Jul 10, 2021 7:54 AM in response to Halliday

Side note for what it's worth: I'm on Big Sur 11.4.


Thank you for replying. I have no doubt that *part* of the issue has to due with how the website itself is handling its performance. However, the other *part* lies with Safari/MacOS. I show no excessive usage when watching videos, yet that incessant message pops up along the top edge stating that the website is using excessive memory and for better performance I should close the website.


I just want the ability to turn off that message from appearing in the first place and stop Safari/MacOS from taking over and reloading the page.


I have this issue with other sites I use on a regular basis. One example is https://steamcommunity.com where simple browsing of the website will periodically trigger the Safari warning.


I don't understand why the user cannot at least have the option to turn off this warning and its associated programming that triggers a website to reload. If the concern is inexperienced users turning this off and not understanding the consequences and/or how to identify issues that warrant investigation, then put the proposed option to deactivate in the 'Advanced' section.


Am I making sense or am I out in left field here? :-)


[Link Edited by Moderator]

Jul 10, 2021 9:03 AM in response to Halliday

Thanks for the link to your previous comments. I've now reviewed them.


While I certainly agree with Mac users contacting the websites to report the issue (and I will definitely be doing so), our workaround shouldn't be to move to a browser that isn't created by Apple. That seems ridiculous. That's like saying my iPhone has an issue with placing calls to landlines managed by Verizon. While I contact Verizon to report the issue, let's just say for whatever reason, if there was a check-box I could click on my iPhone to fix the problem as a temporary workaround until Verizon resolves the issue, but that check-box isn't offered on the iPhone. Therefore, my best workaround option is to use an Android phone.


Seriously though, I get what you're saying, but there should be something we could do as a temporary workaround that doesn't require us to use another browser.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Safari 14 on Big Sur: How to prevent a webpage from automatically reloading because it was using significant memory?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.