Pretraži podršku

Izbjegni prevare podrške. Nikad te nećemo tražiti da nas nazoveš, da nam pošalješ telefonski broj ili da podijeliš osobne podatke. Prijavi sumnjive radnje pomoću opcije „Prijavi zlouporabu”.

Saznaj više

Why is the Firefox mobile (14) service consuming 79MB for the single tab in which I'm entering this question?

  • 4 odgovora
  • 5 ima ovaj problem
  • 1 prikaz
  • Posljednji odgovor od mluna

more options

I love the performance of the new beta, but since install (phone or sd) the prog has gorged on memory. After adding a tab with some media the mem load jumps to 169MB (half the available on my Nexus One). Memory consumption grows so fast that I can't use the app for normal browsing. As mentioned in the question, all this memory is going to the Firefox service not the app. Finally, after returning to the single tab where this text is entered the memory load attributed to Firefox has stabilized around 93MB.

I love the performance of the new beta, but since install (phone or sd) the prog has gorged on memory. After adding a tab with some media the mem load jumps to 169MB (half the available on my Nexus One). Memory consumption grows so fast that I can't use the app for normal browsing. As mentioned in the question, all this memory is going to the Firefox service not the app. Finally, after returning to the single tab where this text is entered the memory load attributed to Firefox has stabilized around 93MB.

Svi odgovori (4)

more options

Hi,

Sorry for the delayed reply to your problem with Firefox for Android beta. Thanks for reporting this issue.

There is an open bug for this, https://bugzilla.mozilla.org/show_bug.cgi?id=760653 with a bit of information about how to mitigate the issue (but, not put much of a dent in it). I've added a note to the bug with a link to your report to see if we can get some more action on it. 

Thanks for helping to test this version and for the feedback!

Regards, Michelle

more options

Michelle I don't believe that bug applies. Frenzy sounds to be describing RAM memory usage not device storage usage which is described in bug 760653.

more options

Thanks kbrosnan, although shifting the app and its storage to the sd is a must, the memory load I was referring to is RAM. That's why I mentioned all that memory being attributed to the Firefox service. Sorry i wasn't quite clear before Michelle and thanks for the response. ~Jerry~

more options

Hey kbrosnan,

Thanks for keeping me honest, it still seems like a bug to me :) Is there another one for the RAM issue we should add to?

-Michelle