{
"$type": "site.standard.document",
"bskyPostRef": {
"cid": "bafyreicqjpykdulq6akpxprutmhh5gtzzelihi4maccwhx4nbzic4oigu4",
"uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3moceas4grqf2"
},
"path": "/viewtopic.php?t=33522&p=275638#p275638",
"publishedAt": "2026-06-15T03:30:56.000Z",
"site": "http://forum.palemoon.org",
"textContent": "> ...\n> Starting today, Protonmail borks Pale Moon and the whole system slows to a crawl. While the login page loads fine, the mess starts once logged in. I can't report it to them because the page never loads properly, and I have to kill the Pale Moon process. Can someone who uses Protonmail check it out? ...\n\nI experienced these exact symptoms the first time I tried to log in to protonmail after updating to PM 34.3.0.1. When I clicked the 'X' to close the tab, it took about 3 minutes for the system to respond, but once the tab closed, everything went back to normal.\n\nNow here's the really odd thing: I have two protonmail accounts. When I log in to one of those accounts everything works as it always has, but when I log in to the other account, I get the behavior ron_1 describes. (I tried this multiple times, clearing all cookies between log-ins, and got the same results each time.)\n\nThe only difference I can see between the two accounts is that the one that fails has a much longer user-name (18 characters), while the account that works as ever has only 6 characters in the log-in user-name.\n\nIt seems unlikely that the length of the name is the culprit, but, like I said, it's the only difference I can see between the two accounts....\n\n(I'm skeptical of the HW acceleration explanation, only because none of my settings have changed, and I was testing these two accounts without changing anything between log-ins. Yet, consistently, one account works like always and the other locks up the whole system as soon as I click the button to sign in. Very bizarre.)\n\n* * *",
"title": "Browser Support • Re: [SOLVED] Protonmail overloading Pale Moon and the system",
"updatedAt": "2026-06-15T03:30:56.000Z"
}