js chrome browser errors - CPU spiking and red "not responding"
So ... I posted about this problem a few weeks ago: (https://support.mozilla.org/en-US/questions/1144546), and it seemed to not be resolved.
I then switched to Chrome - liked a LOT about Chrome; how smooth and fast everything moved. But, there were severe limitations (that impacted the way I use my browser); and I believe I have little option but to return to Firefox.
I downloaded the very newest Firefox 50.0.2, as well as Palemoon, Waterfox and Cyberfox. I imported my bookmarks into each of those (and each time, the same problem occurred as in my original thread. The resource monitor would show the application in red with "not responding." This time, however, I began receiving "unresponsive script errors" (which happened infrequently before) -- like this one: Script: chrome://browser/content/places/editBookmarkOverlay.js:1116
And, of course, while that's happening, I can do nothing else.
So far, I'm tracking each of the browsers (except I can't run Waterfox and Firefox simultaneously) -- and it looks like Palemoon uses the least CPU for similar tasks. However, *all* of them work poorly, for example, on LinkedIn, when replying to messages (I wish there was a way to video the experience for here). Basically, after hitting "reply" the entire message box flashes sporadically, and my typing is delayed significantly.
So far, the normal 6-10 times an hour of freezing hasn't seemed to happen -- then again, these are all fresh new installs (I even uninstalled and deleted Firefox before reinstalling it), and -- so far -- there are no extensions added.
I'd just love to know what I can do to offset this issue, before I begin customizing and reloading extensions (into whichever of the four engines I finally decide upon).
Additional System Details
- User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.99 Safari/537.36
Firefox uses the "chrome://" protocol to access its own internal files and also access files from extensions (no relation with Google Chrome).
In this case the problem is with the places.sqlite database file that Firefox uses to store the bookmarks and history. You can open such a chrome URI via the location/address bar like you open a web page.
- chrome://browser/content/places/editBookmarkOverlay.js (line 1116)
You can check for problems with the places.sqlite database (bookmarks and history) in the Firefox profile folder.
You can create a new profile to test if your current profile is causing the problem.
See "Creating a profile":
If the new profile works then you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over problems.
Is it possible that these issues could be occurring with a new install? I had already uninstalled Firefox (and, in fact, this error was occurring with CyberFox -- built on Firefox (but, ostensibly, with files located in a completely different folder)) ....