{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicajtjngsm2hiqezr6rf4euel2xfbi764qouurpfprzzksm6w7tjq",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mnaxdqrsqq42"
  },
  "path": "/viewtopic.php?t=33469&p=275067#p275067",
  "publishedAt": "2026-06-01T19:44:39.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "I added \"Palemoon.exe\" to ProcessHacker (which is always running in my tray) process notification system a long time ago exactly for the reason Moonchild mentioned above: occasionally the browser might take a while to clean after itself after telling it to shutdown, and my biggest fear is to run into somesort of a race condition where I start a new instance of the browser before the previous instance exited cleanly, and lose any of the permanent data storage I value so much (tabs, cookies, login data, etc).\n\nGranted, I don't think I have seen recent-ish (as in 5~7yrs) iterations of palemoon taking extraordinaire time to shutdown, but my browsing habits are fairly mundane. YMMV.\n\n* * *",
  "title": "Browser Support • Re: Pale Moon response speed under miserable ping times",
  "updatedAt": "2026-06-01T19:44:39.000Z"
}