The main issue I find is that by doing so, a user who may use Salesforce Console may end up seeing a large number of entries, sites or more which then explodes the cache size once this happens and the system doesn’t have any more free cache salesforce may work erratically with all the locked cache but other apps, sites or information may fail as it cannot get access to the Chrome cache for any normal operation. Side note: this is the current thing that worked now I’m currently in the phase of monitoring how large it gets and the cause but in my own more advanced topic/coverage here the default max time that Salesforce keeps old/static entries is about two weeks. You can then go back to the chrome page to monitor the cache usage:Īnd Eureka! The cache is now higher without resetting, clearing your cache and then you can go to the sites that weren’t loading like a new chrome search or even streaming sites and it’ll now load normally. To the end of the shortcut once done, close all chrome.exe processes and then relaunch. So from there I then appended: -disk-cache-size=1000000000 Then with the above take the existing value and compare it to the max cache size: To change this I had to go to the properties on the shortcut To the chrome.exe shortcut to allow more cache to be available. To fix this you can append the flag: -disk-cache-size= YOUR_VALUE_HERE This is right along the same time period where the issues start occuring as a result of the issue then means all other sites may or may not load or stop responding randomly for normal use. Then check the “current size” to “max size” Which all loads fine until you get the “Current size” of the Chrome Cache to meet the “Max Size” of the chrome cache.
In my own tests we have Salesforce console and you can monitor the usage of the current Blockfile cache in tandem with the cache. Further solutions are lackluster as there’s the typical “restart chrome”, “clear your chrome cache” and more which keeps tying to issues with Salesforce excessively using up resources and causing this. In my own tests Chrome used by itself will work fine without any issue then fail once you start using Salesforce Console. Which then readily becomes apparent with the common culprit: Salesforce Console. Further, trying to find anything new will have Chrome stop responding or infinitely load after 5-15+ minutes for a simple search. Often I will be working and then sites such as music streaming or more will stop responding.Įven opening a new google tab to search will then end in failure. So I have worked for various companies and while sporatic the more recent thing I have seen is that the Salesforce Console (lightning) or rather the newer interation that pushes heavy javascript usage ends up causing Chrome to stop responding.
Streaming sites like pandora, siriusxm radio or others just buffer or will not load?Ĭlear the chrome cache and then the issue is fine for a few days or a week then the issue randomly creeps back and is the same old unresponsive mess? Sites like just sit endlessly buffering or never loads anything? Getting Aw Snap errors randomly while you work? Loading or a new search just sits for 5-15+ minutes while loading and you’re on fiber internet or that’s not the issue? Opening a new window and it then spins forever on a new site? Ever had an issue where Chrome stops responding?
0 kommentar(er)
