Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Firefox for Android becomes painfully slow over time. Clearing data fixes, but erases bookmarks. Where is the "Reset" function ??

  • 12 பதிலளிப்புகள்
  • 28 இந்த பிரச்னைகள் உள்ளது
  • 1 view
  • Last reply by John99

After a fresh install, Firefox loads websites very fast with almost no lag. After a few weeks, it becomes slower and slower. Getting to the point where it wil take aboit 20 seconds to display the Top Sites/Bookmarks window. Then sometimes opening a page, the loading circle stops moving and it freezes the phone. After about 15 seconds everything works again. The only way I found to fix this horrendous problem is to go into control panel for Firefox and Clear Data. I dont like doing that because I lose all of my bookmarks. It seems the Cache always shows "0 bytes" so there never is nothing to clear out. I would like to know where this "Reset" function is for Android. I see they have it for Windows versions..but what about Android?

My phone is an HTC Rezound running stock Android 4.0.3 Thanks in advance.

After a fresh install, Firefox loads websites very fast with almost no lag. After a few weeks, it becomes slower and slower. Getting to the point where it wil take aboit 20 seconds to display the Top Sites/Bookmarks window. Then sometimes opening a page, the loading circle stops moving and it freezes the phone. After about 15 seconds everything works again. The only way I found to fix this horrendous problem is to go into control panel for Firefox and Clear Data. I dont like doing that because I lose all of my bookmarks. It seems the Cache always shows "0 bytes" so there never is nothing to clear out. I would like to know where this "Reset" function is for Android. I see they have it for Windows versions..but what about Android? My phone is an HTC Rezound running stock Android 4.0.3 Thanks in advance.

All Replies (12)

Please update to version 19 to get the best performance of Firefox for Android.

This problem has existed in every know version of Firefox for Android since version 15 and earlier. I am very hesitant to update to the latest version because of numerous latest reviews of people having crashing problems with ver. 19. Thanks, but Firefox is the only browser I can use. Every other browser is barely useable since the ICS update on my phone.

Updating does not Clear data in the control panel, and in that data is what's causing the problem.

Speaking of data, here is just how much data Firefox is using.

Bruce0375 மூலமாக திருத்தப்பட்டது

You can try filing a bug for this issue at Bugzilla.

I will do that. Thanks. I just wish they had a Reset function like they do on the Windows version. shame

Ok, so I updated Firefox to version 19. I had a bad feeling about it but did it anyway. Grrr, I shouldn't have. Updated, and when I opened Firefox, it would not load anything at all. Just kept freezing. Would not go to a link nor would it ever load Top Sites/Bookmarks etc. Went into my task manager and seen it was using 50% - 75% CPU constantly. I went to End Task..but of course, Not Responding. Had to Force Stop in Control Panel. Tried loading Firefox again....SAME PROBLEM again. Froze. Force Stop again. Finally after 4 tries, I gave up. I had no choice but to Clear Data in Control Panel. Boy was I dam surprised when I viewed how much data it was using this time. I'll let the image speak for itself.

Of course, after clearing data it works now. But I lost all 30 of my bookmarks....GRRRRRRR

Hi Bruce0375

Really sorry to hear this. I wish I had a device that I can reproduce this problem with so I can work personally with development to get it fixed.

If you have filed a bug, please post the link here. If you haven't filed a bug, please do!

...Roland

I am not using ICS and this could be totally unconnected, but I did have a problem updating to Firefox 19.0.2 on Android. /questions/952954

John99, I don't install to SD card since my Rezound has over 2gb of internal storage. But that last data storage number might make me re-think that.

Roland, no I have not filed a bug report. I was going to last night but not sure exactly what to file it under. Idk what this increasing slowness, lag and freezing are related to. I have seen the numbers in the data size go up and down. It seems the data size isnt the cause, but perhaps what's in the data heap. Corrupted data maybe.. I'll get back if I figure anything new. Bug time I guess......

Bruce,
whilst waiting for Roland to get back you may wish to try this

Enter into the address bar about:memory you get interactive dynamic information about memory usage, and maybe also about:compartments .

That should at least help you see where the memory is going to.

hi Bruce0375:

I would file it under "Firefox for Android", in the "General" component

Cheers!

...Roland

Thanks both of you. I just discovered the about:about query.... interesting. Not trying to go off topic here, but why is it so many of these Android apps simply lack some kind of reference document or a simple readme.txt file? I would never have found any of this stuff if John99 hadn't even mentioned tge "about" pages. Theres so much more there, you'd think they'd point you to it. Pc software comes with documentation, mobile apps should as well. That's frustrating.

Firefox has not been offering mobile or fx-OS for very long and so we are still working on the documentation for them.

Firefox Desktop is better documented, but even there some subjects tend to be considered advanced and are not documented in the ordinary Knowledge Base (KB). The consoles and about: protocols are not therefore documented in the KB. The memshrink developments including about:memory are also relatively new and only used in specialists situations.

The KB may change and evolve in the future, and possibly with increased numbers of volunteers there may be consideration to expanding documentation, but not long ago we were deliberately archiving articles because we were overstretched.