I'm not sure what the details of that control are or what it demands of applications.
"Couldn't load XPCOM" - Browser is completely bricked. Topic is solved
Moderator: trava90
Forum rules
This board is for technical/general usage questions and troubleshooting for the Pale Moon browser only.
Technical issues and questions not related to the Pale Moon browser should be posted in other boards!
Please keep off-topic and general discussion out of this board, thank you!
This board is for technical/general usage questions and troubleshooting for the Pale Moon browser only.
Technical issues and questions not related to the Pale Moon browser should be posted in other boards!
Please keep off-topic and general discussion out of this board, thank you!
-
Moonchild
- Project founder
- Posts: 39633
- Joined: 2011-08-28, 17:27
- Location: Sweden
Re: "Couldn't load XPCOM" - Browser is completely bricked.
Doesn't sound very "smart"
I'm not sure what the details of that control are or what it demands of applications.
I'm not sure what the details of that control are or what it demands of applications.
"Sales hates anything that can't be turned into a confident sentence." - anonymous warehouse worker
"Why debate someone you fundamentally don't trust?" - Dario Amodei
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
"Why debate someone you fundamentally don't trust?" - Dario Amodei
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
-
algorimancer
- New to the forum
- Posts: 2
- Joined: 2026-05-09, 13:22
Re: "Couldn't load XPCOM" - Browser is completely bricked.
The problem mysteriously went away for a while, and Pale Moon reverted to running normally like the problem had never occurred. However, the "Palemoon.exe - Bad Image" pop-up it is back. "...\mozjs.dll is either not designed to run or Windows or it contains an error....", followed by "Couldn't load XPCOM".
As suggested a couple of posts ago, turning-off "Smart App Control" solved it. I agree, the smartness of that control is questionable.
As suggested a couple of posts ago, turning-off "Smart App Control" solved it. I agree, the smartness of that control is questionable.