{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreidmey2t3zvyxd3noiood4c3xrcraupxlhennwn36fljnzgqy5vjam",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3miihtymv2co2"
  },
  "path": "/viewtopic.php?t=33281&p=271724#p271724",
  "publishedAt": "2026-04-02T02:31:43.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "> Is it this part?\n\nI think it's more GlobalHelperThreadState::maxParseThreads, specifically the return below a comment block (which seems to be the warning that Basilisk-Dev mentioned). maxUnpausedIonCompilationThreads is related to Ion which is part of JIT.\n\n\nCODE:\n\n\n    size_tGlobalHelperThreadState::maxParseThreads() const{ if (IsHelperThreadSimulatingOOM(js::oom::THREAD_TYPE_PARSE)) return 1; // Don't allow simultaneous off thread parses, to reduce contention on the // atoms table. Note that wasm compilation depends on this to avoid // stalling the helper thread, as off thread parse tasks can trigger and // block on other off thread wasm compilation tasks. return 1;}\n\n> Is there a build flag for JITless build you put in .mozconfig?\n\nI don't think there's a build-time flag for disabling JIT. Either the support code is added for an architecture or there's no support at all. In run-time however you can disable JIT entirely for webpages by toggling javascript.options.baselinejit in about:config. It's also an option in the Pale Moon Commander extension's Performance => Javascript tab.\n\n* * *",
  "title": "Platform Development • Re: e10s support question",
  "updatedAt": "2026-04-02T02:31:43.000Z"
}