{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreidd3mjc6ni5cqznpqevir3ztuoetxi5ivoow6enrtmoy6qrixzoeq",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mm2r2ow2oom2"
  },
  "path": "/viewtopic.php?t=33437&p=274218#p274218",
  "publishedAt": "2026-05-17T15:36:26.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "> Should a crash occur, it will most likely affect a tab's web content process — and for a different reason entirely — rather than the entire browser, as I would expect with Pale Moon.\n\nYou're missing the point. Look up \"sandbox escape\". Compromised content processes can induce crashes in the parent, often by manipulating the very IPC protocol separating the processes (which is N/A in Pale Moon). Unless Dactyloidae has addressed all applicable e10s/IPC bugs (which have been categorically dismissed in our development where not related to plugins and NPAPI), they are vulnerable through that mechanism to a whole host of overflow, UAF and RCE bugs. Hence my note of caution.\n\n* * *",
  "title": "Browser Support • Re: Why is Pale Moon so slow?",
  "updatedAt": "2026-05-17T15:36:26.000Z"
}