Summary: | Safari Networking high % CPU when Caches/WebKit/ServiceWorkers folder not writable | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Jeff Johnson <opendarwin> | ||||
Component: | Service Workers | Assignee: | youenn fablet <youennf> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | ap, cdumez, webkit-bug-importer, youennf | ||||
Priority: | P2 | Keywords: | InRadar | ||||
Version: | Safari 14 | ||||||
Hardware: | Mac (Apple Silicon) | ||||||
OS: | macOS 11 | ||||||
Attachments: |
|
Description
Jeff Johnson
2021-01-01 07:44:59 PST
I think that this is something we'd consider to be unsupported configuration, but CC'ing other folks for their perspectives. > 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.
Why not using Safari private windows?
(In reply to Alexey Proskuryakov from comment #1) > I think that this is something we'd consider to be unsupported > configuration, but CC'ing other folks for their perspectives. I tend to agree, though it should not be too difficult to fix. > Why not using Safari private windows? Some people including myself would like private browsing by default. However, Safari has several barriers to this. For example, there is no Private Window option in the "New windows open with" preference. Also, the ⌘n keyboard shortcut cannot be successfully redefined to New Private Window in System Preferences, Keyboard, Shortcuts. > it should not be too difficult to fix. This was the hope. It may be unsupported, but perhaps this bug reveals that the architecture of the underlying code is a bit problematic. Created attachment 417268 [details]
Patch
Comment on attachment 417268 [details]
Patch
test failure is unrelated
Committed r271404: <https://trac.webkit.org/changeset/271404> All reviewed patches have been landed. Closing bug and clearing flags on attachment 417268 [details]. |