Created attachment 480621 [details] heaptrack capture # Symptoms I have https://app.invoicing.co (a.k.a. https://react.invoicing.co/demo) set up as an Epiphany web app running on Fedora 44's WebKitGTK 2.52.5, and after a few hours of simply using the tasks timer feature, I inevitably end up with a WebKitWebProcess that eats 1.5 to 1.6 GB. On initial start on that tasks page, the process uses about 400 MB. Then if I reload the page, it instantly goes to 570 MB. Another reloads bumps it to 650+ MB. Then 720 MB. Then 808, 862, 911 MB, and so on. It might sometimes shrink a little bit (ex: 10%) while the OS is under memory pressure, but not significantly. In any case, after some hours of use, I always end up in the ~1.5 GB territory for that single page in a single WebKitWebProcess. It happens whether or not ad blockers are activated. # Steps to reproduce Run: /usr/libexec/webkitgtk-6.0/MiniBrowser --private https://react.invoicing.co/demo Then navigate to "Tasks", then reload a couple of times, while looking at the process' RAM usage in gnome-system-monitor. In comparison, Chromium manages to keep it at 160-200 MB even if you reload dozens of times, and Firefox also manages to shrink it to ~240 MB. # ProfilinG/measurements From https://blogs.igalia.com/plampe/wpe-memory-leak-investigation-playbook/ : Doing a `stress --vm 1 --vm-bytes 13100M --vm-keep` to memory pressure it by filling my system RAM at 90%+, I see that the webkitwebprocess's RAM usage shrinks by barely 10%, i.e. it might go back to 950 MB from 1.1 GB. Then I ran this: WEBKIT_DISABLE_SANDBOX_THIS_IS_DANGEROUS=1 Malloc=1 /usr/libexec/webkitgtk-6.0/MiniBrowser --private https://react.invoicing.co/demo …combined with: heaptrack -p theProcessIDofWebKitWebProcess …and we have the resulting .zst heaptrack file, which says, "peak RSS: 1.2 GB, total memory leaked: 427 MB" I'm attaching the heaptrack .zst capture file and screenshots.