{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiciwxu4ik4h46nkekxap6veicu4dmv2n7bdeuekoyrnyx6vrazd3a",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3miglegsambu2"
  },
  "path": "/viewtopic.php?t=33281&p=271684#p271684",
  "publishedAt": "2026-04-01T10:06:24.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "It's not technically confined to one core even now as it is, being multi-threaded application. Some captchas get it to put good load on multiple cores.\n\nSingle thread can also be migrated between CPUs. If you want to actually confine it to one core, then you would have to set process affinity accordingly.\n\nBut, considering current code base is a mess as-it-is (IMHO) and workability and reliability of classic extensions under e10s is under question... Firefox seemed fine back in the day, then they kept piling shit on top and it kept getting slower and buggier. Considering issues encountered throughout my years of using Pale Moon, it still has that sting of its Firefox heritage to it.\n\nBut Firefox today isn't better, recently used it on a laptop at home with 4 GB of RAM, it crashed on me literally (just the tab, not whole browser) every 5 min with 2 tabs at most. Floorp (version based on Fx 148) at work today randomly decided to crash on start (plenty of RAM free).\n\nTo say I'm frustrated over the state of modern web browsers in general is an understatement. So far, nobody demonstrated that implementing e10s would solve all our problems, more like replacing one set of problems with another.\n\n* * *",
  "title": "Platform Development • Re: e10s support question",
  "updatedAt": "2026-04-01T10:06:24.000Z"
}