Cerca nel supporto

Attenzione alle mail truffa. Mozilla non chiederà mai di chiamare o mandare messaggi a un numero di telefono o di inviare dati personali. Segnalare qualsiasi attività sospetta utilizzando l'opzione “Segnala abuso”.

Ulteriori informazioni

Questa discussione è archiviata. Inserire una nuova richiesta se occorre aiuto.

Corrupted tabs in 29 and memory leaks (firefox crashing after 5 minutes)

  • 2 risposte
  • 23 hanno questo problema
  • 1 visualizzazione
  • Ultima risposta di Templayer

more options

I've used version 29 for 24 hours and then I had to downgrade back to 28. 29 seemingly randomly corrupts tabs (with a white screen), when they are loaded after a session restore for example (and the history doesn't show the adress they were at for some reason, so I had to manually find the URLs). Also, firefox 29 crashes after 5 minutes. Almost exactly 5 minutes. The layout looks completely the same as other browsers (another major disdain ... like the absence of the download manager button, having to find it everytime in the context menus instead). The memory leakage in 29 is insane (over 1 GB of RAM usage after starting ? What the .... ? 28 has usually around 250 MB). Due to 29 being unusable, I had to revert into 28. If the browser forces me to upgrade into 29, then I will be forced to uninstall it and use a different browser. Also, I am not the only one with the same problem and the same solution in the case of being forced to use 29 by some automatic update if the case arises.

I've used version 29 for 24 hours and then I had to downgrade back to 28. 29 seemingly randomly corrupts tabs (with a white screen), when they are loaded after a session restore for example (and the history doesn't show the adress they were at for some reason, so I had to manually find the URLs). Also, firefox 29 crashes after 5 minutes. Almost exactly 5 minutes. The layout looks completely the same as other browsers (another major disdain ... like the absence of the download manager button, having to find it everytime in the context menus instead). The memory leakage in 29 is insane (over 1 GB of RAM usage after starting ? What the .... ? 28 has usually around 250 MB). Due to 29 being unusable, I had to revert into 28. If the browser forces me to upgrade into 29, then I will be forced to uninstall it and use a different browser. Also, I am not the only one with the same problem and the same solution in the case of being forced to use 29 by some automatic update if the case arises.

Soluzione scelta

After Firefox 28 spammed me for what felt like million times to upgrade to the broken 29 (and the 1 update after that), I've started using chrome instead. I'm pretty sure I wasn't the only one to do that. Chrome doesn't leak memory for me, it doesn't crash, doesn't spam me, and I've found the same extensions I was using for Firefox (iTube studio works with it, tracker blocking does, HTML5 player disabling, Smart Youtube ....) in Chrome.

SO .... why should I use Firefox at all ? Currently, it is worse than Chrome in every way. Problem solved.

Leggere questa risposta nel contesto 👍 2

Tutte le risposte (2)

more options

Hi Templayer, There was an update that went out yesterday 29.0.1. My apologies for being behind on updates.

I am sorry to hear about the memory leak as well. Did this also happen in Safe Mode when you were on version 29?

It may also be helpful to gather the graphics information from the about:support page. Upgrade your graphics drivers to use hardware acceleration and WebGL

more options

Soluzione scelta

After Firefox 28 spammed me for what felt like million times to upgrade to the broken 29 (and the 1 update after that), I've started using chrome instead. I'm pretty sure I wasn't the only one to do that. Chrome doesn't leak memory for me, it doesn't crash, doesn't spam me, and I've found the same extensions I was using for Firefox (iTube studio works with it, tracker blocking does, HTML5 player disabling, Smart Youtube ....) in Chrome.

SO .... why should I use Firefox at all ? Currently, it is worse than Chrome in every way. Problem solved.