315236 2026-05-20 15:19:30 -0700 Content rule list store may end up copying compiled bytecode files 2026-05-21 10:32:12 -0700 1 1 1 Unclassified WebKit WebKit Misc. WebKit Nightly Build Unspecified Unspecified RESOLVED FIXED https://bugs.webkit.org/show_bug.cgi?id=315135 InRadar P2 Normal --- 252846 267774 291796 1 aperez aperez nekohayo webkit-bug-importer oldest_to_newest 2212696 0 aperez 2026-05-20 15:19:30 -0700 When compiling a JSON rule list, the flow is roughly: 1. Calculate the destination location for the compiled file. 2. Create a temporary file, using WTF::openTemporaryFile(). 3. Write compiled bytecode to the temporary file. 4. Delete the destination file (if exists). 5. Use WTF::moveFile() to “rename” the temporary file in the final location. The issue here is that (2.) uses a platform-dependent temporary directory for created temporary files, and for some ports it can easily end up being in a file system different than the final destination, resulting in WTF::moveFile() falling back to a *synchronous* copy. Case example: the GTK and WPE ports use g_get_tmp_dir() for the temporary file location, which most of the time will be /tmp. On modern Linux distributions and embedded devices this can very easily be in-memory (tmpfs), and/or the user's home directory (where programs will configure the ContentRuleListStore data directory) may be on its own volume. 2212714 1 aperez 2026-05-20 16:02:04 -0700 Pull request: https://github.com/WebKit/WebKit/pull/65336 2212998 2 ews-feeder 2026-05-21 10:31:23 -0700 Committed 313681@main (0a4e6af65950): <https://commits.webkit.org/313681@main> Reviewed commits have been landed. Closing PR #65336 and removing active labels. 2212999 3 webkit-bug-importer 2026-05-21 10:32:12 -0700 <rdar://problem/177635088>