Safari 14 + Big Sur + Cookie 6 = runaway Safari Networking
-
Hi,
Using Safari 14.0.1 (16610.2.11.51.8) on Big Sur 11.0.1
I've been having problems with the Safari Networking process pegging at 100% CPU utilization. Looking for the source, I checked out the Console and noticed it being spammed with the following message:
com.apple.Webkit.Networking (WebCore) Failed to store registration data into records table (6922) - <private>This seems to only occur with Cookie running... I've disabled other extensions but it hasn't helped.
Thank you for any help you might be able to offer.
-
Follow-up: de-selecting deleting of cache seems to have fixed this. Without cache-clearing, Cookie is running w/o runaway processes.
-
Hello Cookie Tech Support - Following up here...Has this issue been fixed with the Cookie cache clearing feature under Safari 14 and Big Sur?
I'm having the identical problem as CaptainProton with the "Safari Networking" process dominating my CPU time and draining my battery (2020 MBP13 that is supposed to run 15 hours barely runs 3.5 when this process is stuck at 200% CPU time). Quitting Cookie and Safari most times stops this (after a while) but sometimes you have to restart the system. It will come back again with time.
I'm running Safari Version 14.0.2 (16610.3.7.1.9) and MacOS Big Sur 11.1
I'm also having issues with Google ReCAPTCHA not working for secured sites. When you click the "I'm not a robot" checkbox, the ReCAPTCHA just hangs - you don't get the security challenge photos. Quitting Cookie and reloading the webpage works.
I'm a 5+ year user of Cookie and prefer to not abandon it for a competitive product but will have to move if these issues are not addressed. Thank you.
-
@SweetP Hello SweetP support - is there any update here? If I can't get this fixed, I sadly will have to find another product and uninstall Cookie. It does not look like the tech support section is being updated very often, which makes me doubtful. Thank you.
-
You need to disable cache removal while safari is running. I don’t recommend removing data while your browser is open.
-
@sweetp Thank you, I un-checked Caches last week once I read this post but have still had times where Safari Networking process starts dominating CPU time. Any other suggestions?
Also - did you see my 2nd question about Cookie 6 interfering with ReCAPTCHA?
-
Im pretty sure that is also related to cache removal while Safari is running
-
Hi @sweetP. Unfortunately not. Just tested it on the following "test" website and once you click the "I'm not a robot" button you just get a spinning wheel. The photo tiles for validation never appear. If I quit Cookie, restart Safrri and reload the page, it instantly works.
-
@blsmithf13 I don't see a way around this. I just tested, and as long as Safari is closed when you remove the cache - when you restart Safari, recaptcha should work.
you can test this manually quite easily, navigate to this file:
~/Library/Containers/com.apple.Safari/Data/Library/WebKit/WebsiteData/ResourceLoadStatistics/observations.db- remove it while Safari is running - recaptcha breaks on next page reload until a restart.
- remove it when Safari is Quit, upon relaunching recaptcha works.
If you have an SQLite viewer, you can open the file, and see that it stores a record of every site Safari pings. So it's not really feasible to NOT delete it.
The solution is to only remove cache while Safari is Quit.
This has always been the recommended approach to clearing data from you browser.Thats why there's a warning right inside Cookie on the Removal Options tab, and also when you try to remove any data while your browser is open...
This may have worked in the past, but has broken now, as Safari has changed its behaviour as to how it deals with this data. Im sorry I dont have better news, theres only so much Cookie can do.
-
I have exactly this problem as well. I normally run with the Timer set to delete selected data every five minutes. Unfortunately, this Timer state initiates a process called Safari Networking, which takes up 100% to 150% CPU when examined with Activity Monitor. The problem is solved by turning off the Timer function. Unfortunately, I need the Timer function.
This issue reduces my battery operation time (mid-2015 MacBook Pro) from about 6 hours to about 2 hours. I hope Sweet P is working this issue. I'm unable to use the product with Safari, and I'm looking at alternatives.
-
Can concur, same issue here. M1 MBA, noticed that I got a terrible battery life, just 2 or 3 hours before I discovered that Safari Networking was pegged at 100% every time I took the machine out of sleep after a few hours.
-
Having the very same problem under Mac OS Mojave and Cookie version 6.5.3. My 2015 MacBook Air is heating up like crazy, battery life has gone way down, etc.
Activity Monitor shows Safari Networking going crazy -- 110% CPU, etc.
Console shows "Failed to store registration data into records table" repeatedly appearing.
Had hoped that the latest version would fix this!
I am confused on one point, however. Do I uncheck Caches under "Unwanted Data" or under "Timer Options"?
It sounds as if it's the one under Timer Options. Or, is it both?
Look forward to hearing back. Thanks!
-
you should uncheck cache removal under Timer Options
-
Thanks for the confirmation. The problem still occurs even with Caches UNCHECKED! I end up force quitting the Safari Networking process from the Activity Monitor or simply quitting Safari.
So, it seems that Cookie is no longer implicated -- at least not the Cache setting!
Any other ideas of what could be causing this? Is there some known Safari glitch that does this?
By the way, I'd suggest changing the wording under the Unwanted Data tab. I'd recommend adding the phrase "Non-Timer" so it would read "Select Unwanted Data for Non-Timer Automatic Removal. (See Timer Options tab for those choices.)"
That would clear up some of the confusion, although it doesn't solve the run-away Safari Networking!
-
hmmm,
try disabling Cookie for a while to rule out that it is actually Cookie causing the issue
