UPGRADED TO 49.0.2, CAN'T EVEN USE THE DAMN BROWSER NOW~!!!!! IDIOTS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
plugin-container just grows and grows and grows. CAN'T EVEN USE THE DAMN BROWSER AFTER UPGRADE!!!!!!!!!!!!!!!!!!! DO THESE MORONS EVER TEST UPGRADES BEFORE ROLLING OUT??????????????????????????? IDIOTS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Toutes les réponses (5)
Firefox is now UN-FUCKING USUABLE!!!!!!!!!!!!!!!!!!!!!! NICE JOB IDIOTS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
What didn't you like moses the FUCK or the YOU?
Hey, you're not the first person with this problem and you do not need to take it personally. Mozilla isn't out to get you, and profane venting doesn't really draw more support resources to your situation.
One of the headline changes in Firefox 48-49 is e10s, which separates the browser interface process from the page content process -- page content goes into plugin-container.exe which you noticed ballooning in size. The performance impact of this can vary a lot between systems: many users find it faster, some find it slower, for many it's neutral. Hopefully by the time all the kinks are worked out it will work smoothly for everyone.
Are you using e10s?
Based on your remarks about plugin-container.exe I assume so. But you can check whether you have this feature turned on as follows. Either:
- "3-bar" menu button > "?" button > Troubleshooting Information
- (menu bar) Help > Troubleshooting Information
- type or paste about:support in the address bar and press Enter
In the first table on the page, check the row for "Multiprocess Windows" and see whether the number on the left side of the fraction is greater than zero. If so, you are using e10s.
If you are using e10s:
To help evaluate whether that feature is causing this problem, you could turn it off as follows:
(1) In a new tab, type or paste about:config in the address bar and press Enter/Return. Click the button promising to be careful.
(2) In the search box above the list, type or paste autos and pause while the list is filtered
(3) Double-click the browser.tabs.remote.autostart.2 preference to switch the value from true to false
Note: the exact name of the preference may vary, but it will start with browser.tabs.remote.autostart
At your next Firefox startup, it should run in the traditional way. Any difference?
Modifié le
That solved one problem and caused another now the Firefox exe is using all of the memory and CPU. Thank you for your help but I don't need you to tell me what kind of language to use and I don't recall saying Mozilla was out to get me. I worked in IT for over 20 years, 5th graders could do a better job of rolling out an update. You either allowed it to be rolled back, or you allow the feature to be turned off easily. As I stated, do these Morons ever test things?
I only wanted to be sure I had the latest security features, and I went from a browser I could use (even if I had to limit functions) to one I can't use at all. That's ridiculous.
Of course releases are tested. You're being facetious, right? Major releases typically have a 12 week test cycle: 6 weeks as the Developer Editor, 6 weeks as Beta. Critical patches, on the other hand, may be tested for a week or less since they are deemed critical.
What version were you using before? That may help flag up key changes between that and the current version.
More generally:
- Have you tested in Firefox's Safe Mode to rule out an extension conflict? See: Diagnose Firefox issues using Troubleshoot Mode.
- These could be useful checklists: