Avatar for Username

Kërkoni te Asistenca

Shmangni karremëzime gjoja asistence. S’do t’ju kërkojmë kurrë të bëni një thirrje apo të dërgoni tekst te një numër telefoni, apo të na jepni të dhëna personale. Ju lutemi, raportoni veprimtari të dyshimtë duke përdorur mundësinë “Raportoni Abuzim”.

Mësoni Më Tepër

Kjo rrjedhë është arkivuar. Ju lutemi, bëni një pyetje të re, nëse keni nevojë për ndihmë.

FIREFOX 35 UPDATE AND LINKEDIN SLOWDOWN - GOOGLE TRANSLATE EXTENSION ISSUE

  • 1 përgjigje
  • 1 e ka hasur këtë problem
  • 4 parje
  • Përgjigjja më e re nga Mike

Mike
Mike
more options

I've had Firefox since FF 9 and never any problems, skipping FF 16 update, other than my mismatched analog monitor and digital graphics card not liking hardware acceleration so it's been OFF since FF 28 and worked great. I keep plugins and extension both current. By the time I got to 32, the mysterious hardware acceleration cleared up and it was back on with no problems anywhere. Turning it off in the FF Tools never made any difference, I had to use the DISPLAY feature under CONTROL PANEL

I updated from FF 32 that had no problems to FF 34 and instantly had huge memory leaks composing text in Firefox's PULSE page. Killing ADBLOCK PLUS solved that problem but still left a similar problem composing on the DISCUSSIONS PAGE. Clearing Cache and Cookies made no difference. Somewhere in there, LinkedIn revised the discussions page with ads and removed the ACTIVITY FEED section https://www.linkedin.com/today/post/article/firefox-ad-block-plus-linkedin-jam-mike-trumbature?trk=mp-reader-card

Going back to FF 32 solved both the discussions problems somewhat. Updating to FF 35 made them worse. Running the gauntlet with the extensions once more, individually toggling off and back on found Google Translate the problem this time. https://www.linkedin.com/today/post/article/firefox-ad-block-plus-linkedin-jam-mike-trumbature?trk=mp-reader-card. Once both PULSE and the discussions title and comment dialog boxes worked OK, I reactivated ADBLOCK PLUS and it worked with no problems.

Instead of disabling all the extensions or running safe mode, I keep Task manager ON TOP, disabled one extension at a time, reset Firefox (reset extension button) and reloaded troubled pages looking for improvements. If it made no change, the extension was enabled and another disabled and the process repeated. Resetting Firefox each time lets you start over fresh each time using Task Manager for comparison.

I nave four tabs open now, including LinkedIn PULSE and this one at the bottom of this dialog box. FF memory is 344 MB steady, no increases, and 1% - 3% CPU when idle, no activity. Worked for me.

I've had Firefox since FF 9 and never any problems, skipping FF 16 update, other than my mismatched analog monitor and digital graphics card not liking hardware acceleration so it's been OFF since FF 28 and worked great. I keep plugins and extension both current. By the time I got to 32, the mysterious hardware acceleration cleared up and it was back on with no problems anywhere. Turning it off in the FF Tools never made any difference, I had to use the DISPLAY feature under CONTROL PANEL I updated from FF 32 that had no problems to FF 34 and instantly had huge memory leaks composing text in Firefox's PULSE page. Killing ADBLOCK PLUS solved that problem but still left a similar problem composing on the DISCUSSIONS PAGE. Clearing Cache and Cookies made no difference. Somewhere in there, LinkedIn revised the discussions page with ads and removed the ACTIVITY FEED section https://www.linkedin.com/today/post/article/firefox-ad-block-plus-linkedin-jam-mike-trumbature?trk=mp-reader-card Going back to FF 32 solved both the discussions problems somewhat. Updating to FF 35 made them worse. Running the gauntlet with the extensions once more, individually toggling off and back on found Google Translate the problem this time. https://www.linkedin.com/today/post/article/firefox-ad-block-plus-linkedin-jam-mike-trumbature?trk=mp-reader-card. Once both PULSE and the discussions title and comment dialog boxes worked OK, I reactivated ADBLOCK PLUS and it worked with no problems. Instead of disabling all the extensions or running safe mode, I keep Task manager ON TOP, disabled one extension at a time, reset Firefox (reset extension button) and reloaded troubled pages looking for improvements. If it made no change, the extension was enabled and another disabled and the process repeated. Resetting Firefox each time lets you start over fresh each time using Task Manager for comparison. I nave four tabs open now, including LinkedIn PULSE and this one at the bottom of this dialog box. FF memory is 344 MB steady, no increases, and 1% - 3% CPU when idle, no activity. Worked for me.

Krejt Përgjigjet (1)

Mike
Mike I zoti i pyetjes
more options

Firefox still will not release the memory when a tab is closed but at least it's not adding a lot opening new tabs and running away or locking up the processor while doing nothing or typing a few strings of text.

One of the best workarounds I've had with dialog box seizures was to compose all the text on a Word document with MS Word or Google Docs, edit then copy and paste the text into Pulse or a discussion dialog box. This also works on sites like this, emails, etc. Yahoo email had the same problem composing emails with hardware acceleration on.