{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihypovpg3ddk6o2svz7c2wpjr2744ededb3s7mnosjne2e6k622tu",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mj5v6szvk3e2"
  },
  "path": "/viewtopic.php?t=33306&p=272163#p272163",
  "publishedAt": "2026-04-10T17:08:53.000Z",
  "site": "http://forum.palemoon.org",
  "tags": [
    ".mozconfig.zip",
    "cpu-ram-mon@drugwash.zip"
  ],
  "textContent": "> I'd likely use it semi-normally for light tasks [...], and then start closing stuff very quickly\n\nI'm not sure how the OS behaves, if it caches stuff even after apps were closed. Not to mention internal bugs, memory leaks etc. Cinnamon is known to \"grow\" in time memory-wise (and not only), at least in older versions like mine (4.2). So it may not be so safe to open and close applications during a build hoping all memory will be freed immediately and without gaps. I'd rather be on the safe side than spend another 2+ hours for a subsequent build.\n\nAlso I noticed there are a few parts - as in more than one - of the build process where RAM usage increases more or less significantly but not as much as the linkages you mentioned. Still kinda dangerous to use other apps concurrently.\n\nHere's the .mozconfig I use:\n\n.mozconfig.zip\n\nYou may get this applet and install it in your virtual machine. It may not display all fields - it'd need a real, bare metal installation for that, including an NVIDIA video card - but hopefully it will display the amount of memory used and maybe CPU usage percent as well. It will need the Noto Color Emoji font installed.\nAlso please note a vanilla OS installation might be lighter on resource usage than mine.\n\ncpu-ram-mon@drugwash.zip\n\n* * *",
  "title": "Browser Development • Re: 34.2.0 build failed, --enable-jxl unknown ??",
  "updatedAt": "2026-04-10T17:08:53.000Z"
}