RESOLVED FIXED 204779
Resource Load Statistics (experimental): Delete non-cookie website data after 7 days of no user interaction
https://bugs.webkit.org/show_bug.cgi?id=204779
Summary Resource Load Statistics (experimental): Delete non-cookie website data after...
John Wilander
Reported 2019-12-02 18:53:15 PST
Trackers are continuing to move cross-site tracking IDs into first-party storage. We should age out script-writable non-cookie website data in alignment with the 7-day cap on client-side cookies.
Attachments
Patch (103.89 KB, patch)
2019-12-02 19:23 PST, John Wilander
no flags
Radar WebKit Bug Importer
Comment 1 2019-12-02 18:53:43 PST
John Wilander
Comment 2 2019-12-02 19:23:50 PST
John Wilander
Comment 3 2019-12-03 05:59:55 PST
The Win test failures are all over the place and seem unrelated.
Alex Christensen
Comment 4 2019-12-03 15:49:26 PST
Comment on attachment 384681 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=384681&action=review > Source/WebKit/NetworkProcess/Classifier/WebResourceLoadStatisticsStore.cpp:488 > + postTask([this, mode, completionHandler = WTFMove(completionHandler)]() mutable { Not for this patch, but I don't like it how in this one file it's ok to use this without protecting it or checking a weak pointer, but everywhere else we need to be careful. Let's make it so postTask doesn't implicitly protect this and require all callers to protect this.
Chris Dumez
Comment 5 2019-12-03 15:51:07 PST
(In reply to Alex Christensen from comment #4) > Comment on attachment 384681 [details] > Patch > > View in context: > https://bugs.webkit.org/attachment.cgi?id=384681&action=review > > > Source/WebKit/NetworkProcess/Classifier/WebResourceLoadStatisticsStore.cpp:488 > > + postTask([this, mode, completionHandler = WTFMove(completionHandler)]() mutable { > > Not for this patch, but I don't like it how in this one file it's ok to use > this without protecting it or checking a weak pointer, but everywhere else > we need to be careful. Let's make it so postTask doesn't implicitly protect > this and require all callers to protect this. Previously it was like that and people kept forgetting to protect this and we had tons of similar crashes. As a result, I made postTask() protect this. Worse case scenario, the caller protects again, which is a bit inefficient but at least does not cause crashes.
John Wilander
Comment 6 2019-12-03 17:57:50 PST
Thanks for the review!
WebKit Commit Bot
Comment 7 2019-12-03 18:41:58 PST
Comment on attachment 384681 [details] Patch Clearing flags on attachment: 384681 Committed r253082: <https://trac.webkit.org/changeset/253082>
WebKit Commit Bot
Comment 8 2019-12-03 18:41:59 PST
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.