[Webkit-unassigned] [Bug 220220] New: Safari Networking high % CPU when Caches/WebKit/ServiceWorkers folder not writable
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Fri Jan 1 07:44:59 PST 2021
https://bugs.webkit.org/show_bug.cgi?id=220220
Bug ID: 220220
Summary: Safari Networking high % CPU when
Caches/WebKit/ServiceWorkers folder not writable
Product: WebKit
Version: Safari 14
Hardware: Mac (Apple Silicon)
OS: macOS 11
Status: NEW
Severity: Normal
Priority: P2
Component: Service Workers
Assignee: webkit-unassigned at lists.webkit.org
Reporter: opendarwin at lapcatsoftware.com
When the Caches/WebKit/ServiceWorkers folder is not writable, the Safari Networking process has very high CPU usage (near 100%), due to logging error messages nonstop.
Steps to reproduce:
1) Delete the contents of the folder ~/Library/Containers/com.apple.Safari/Data/Library/Caches
2) Lock the folder ~/Library/Containers/com.apple.Safari/Data/Library/Caches in Finder
3) Launch Safari
4) Open https://www.youtube.com
5) Play a video
6) Launch Activity Monitor and view % CPU
7) Launch Console and view messages
I found the problem by also noticing the "logd" process high in Activity Monitor, which inspired me to check the Console log. I saw the following errors over and over again:
com.apple.WebKit.Networking os_unix.c:44500: (2) open(/Users/bigsir/Library/Containers/com.apple.Safari/Data/Library/Caches/WebKit/ServiceWorkers/ServiceWorkerRegistrations-5.sqlite3) - No such file or directory
com.apple.WebKit.Networking Failed to open Service Worker registration database
com.apple.WebKit.Networking cannot open file at line 44499 of [02c344acea]
I've reproduced this issue with macOS 11.1 (20C69) and Safari 14.0.2 (16610.3.7.1.9) on an Apple silicon Mac mini, and also with macOS 10.14.6 (18G7016) on an Intel MacBook Pro.
I had locked the Safari Caches folder because it tends to get enormous on disk for no good reason. I don't need or want anything to be cached on disk after I quit Safari.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20210101/2fbf37fb/attachment.htm>
More information about the webkit-unassigned
mailing list