com.apple.WebKit.Networking (Safari Networking) process caught in an error loop/hang
I have recently encountered intermittent cases of the Safari Networking (com.apple.Webkit.Networking) process suddenly consuming unusually high power and CPU percentages on a continuing basis until I force quit the process in Activity Monitor. I haven't been able to reliably replicate the loop/hang but it seems to be related to opening or closing at least some Safari web tabs or pages.
I first notice it when my 2019 16" MacBook Pro fans unexpectedly ramp up from ~1,800 to >3,500 rpm, system power consumption jumps from ~25w to 50-60w (iStat Menus data) and Activity Monitor shows "Safari Networking" at 100%+ CPU (single core?) usage. Once Safari Networking ramps up, it stays at these levels until I force quit the process, after which it automatically restarts and settles down to more normal CPU usage - until the next time. This happens several times a day and I have left it running in a high CPU usage state for more than 20 minutes before resorting to the force quit. Neither restarting Safari nor rebooting the MacBook seem to resolve the issue.
I am running Mac OS Catalina 10.15.7 and Safari 14.0.1. Note that 1) I have encountered the issue both with and without my 3 Safari extensions enabled and 2) I do not use Safari to save or autofill password/login data, preferring 1Password to handle that chore.
Examining the console logs during the loop/hang shows one of the two following error messages being written to the Console log multiple times per second until a process force quit:
error 13:49:06.721376-0700 com.apple.WebKit.Networking Failed to remove registration data from records table (6922) - <private>
or
error 10:18:53.925329-0700 com.apple.WebKit.Networking Failed to store registration data into records table (6922) - <private>
This sounds like it could be a file permissions or corruption issue, but where does Safari keep apparently open tab/site "registration data" in a "records table"?
Given the intermittent nature of the issue, I have not tried booting into Safe Mode until I can determine a way to reliably trigger the problem. My next step is to download and run the current Catalina Combo Updater. I'll update this note if that resolves the issue but I welcome any insight from others that might steer me in the right direction.
Rick