Over and over again, when using Firefox browser, a window pops up with the message:
Unresponsive script: xpcomutils.jsm:357
which is normally followed by another popup window stating nsPropmpter error.
The thing is, the entire operating system becomes unusable. COMPLETELY UNUSABLE! Cairo (GLX Dock) CPU meter slams to the hilt, the mouse is unresponsive, and the hard drive LED stays constantly lit.
This can go on for 5 to 10 minutes. Sometimes it takes 5 minutes for the window to pop up asking to stop the script. The entire operating system is unusable at this point.
Why is a browser script slamming my hard drive like that? A browser script should not be hitting the hard drive.
This is a very serious issue that Ubuntu needs to address with Firefox. It renders the entire operating unusable.
$ locate XPCOMUtils.jsm /home/grpace/.wine/drive_c/windows/system32/gecko/1.0.0/wine_gecko/modules/XPCOMUtils.jsm
I have a dual-boot with Ubuntu 12.04 and Win XP. They are on separate hard drives. I don't use XP anymore unless absolutely necessary. However, fstab loads those Windows partitions on Ubuntu startup.
How is Firefox or a possible Firefox plugin running on Ubuntu accessing the Windows partitions on a separate drive?
Quite peculiar. What plugin would decide to install itself using Wine and on a completely separate drive?