{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreievcgl5pl4cd2gjmf6u54l62zugxhfh2lseugq5xao7ybjfqmhvga",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mkpbywdbwi22"
  },
  "path": "/viewtopic.php?t=33382&p=273030#p273030",
  "publishedAt": "2026-04-30T08:59:01.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "> If this is right... does that mean this was using 12 parse threads before my old quad core started having an application freeze with a fresh profile, and backing off to 11 was what made it rock solid stable for me?\n\nIf it is a 4 core 8 HT CPU, then yes, you were trying to parse 12 things in parallel on a CPU that would have a capacity of ~5-6 cores worth of power, so effectively you hit the deadlock hitting a load of twice the capacity of what your CPU could handle at 100%. Considering the complexity of parsing JS, that isn't really a surprise.\n\n* * *",
  "title": "Platform Development • Re: The browser hang with 0 CPU load.",
  "updatedAt": "2026-04-30T08:59:01.000Z"
}