{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreieltkajcqqordv6c4n5kmkyrwwowc6rio2ptmaoehrgpvtk2etngi",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mkmkqicyftw2"
  },
  "path": "/viewtopic.php?t=33382&p=272957#p272957",
  "publishedAt": "2026-04-29T05:37:52.000Z",
  "site": "http://forum.palemoon.org",
  "tags": [
    "https://repo.palemoon.org/MoonchildProd ... 0c6db7c47b"
  ],
  "textContent": "So... good news and bad news. Reverting this commit fixes it:\n\nhttps://repo.palemoon.org/MoonchildProd ... 0c6db7c47b\n\nThat is, I cannot reproduce whatever is causing this crash anymore if I revert the commit that stops limiting parse threads to 1. So while the rest of Basilisk-Dev's changes appear innocent here, whatever he did just wasn't quite enough to make it 100% safe for us to use more than one parse thread. Mozilla probably assumed it was just the WASM stuff, but may have not noticed everything else that had to change to make it safe to do that.\n\nIt's kind of a shame, because it works most of the time... but in a few specific situations, like being on a fresh profile with a very busy web page, it crashes. So the good news is we can stop it from happening... the bad news is we are stuck with a single-threaded parser which is not ideal...\n\n* * *",
  "title": "Platform Development • Re: The browser hang with 0 CPU load.",
  "updatedAt": "2026-04-29T05:37:52.000Z"
}