Bug 236760
| Summary: | /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitNetworkProcess allocates 85 GB | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Joris <joris.geer> |
| Component: | WebKitGTK | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED INVALID | ||
| Severity: | Normal | CC: | bugs-noreply, mcatanzaro |
| Priority: | P2 | ||
| Version: | Other | ||
| Hardware: | Mac (Intel) | ||
| OS: | Linux | ||
Joris
The WebKitNetworkProcess process allocates 85 GB.
/proc/<pid>status shows :
VmPeak: 117607928 kB
VmSize: 85772212 kB
The parent process is xreader (a PDF document viewer) which indeed links to WebKit.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Michael Catanzaro
Hi, that's just virtual memory required by JavaScriptCore's Gigacage. Note that is *virtual* memory, i.e. address space. This is needed to maintain segregated heaps for different object types. It doesn't actually consume resident memory.
I'm impressed the xapp developers made the app work on macOS. They weren't kidding about their apps being cross-desktop. Honestly, I didn't know that it was still possible to build WebKitGTK on macOS at all!