Эта тема была архивирована. Если вам нужна помощь, задайте новый вопрос.
Web pages do not resolve
There has been a sudden failure to resolve the graphics of websites I attempt to access in Firefox. I am using a Galaxy tab S2 with android 5.0.2.
Any attempt to view a website which uses graphics produces a few blocks of colour and maybe some black dots where the text is meant to be. This is a sudden change in performance. I don't get the same problem on other android devices or with windows 10.
Repeated uninstall / reinstall cycles have not improved matters. Firefox nightly produces the same result. It is possible that there is some incompatibility with a recent Guardian (newspaper) beta installation but that has been replaced with the stable public version without any improvement in Firefox performance. There are no associated crash reports.
Can anyone offer any assistance in diagnosing what is going on and correcting the problem please
Just a quick note to confirm that this (as mentioned above) should be fixed in a forthcoming update.Прочитайте этот ответ в контексте 👍 1
Все ответы (18)
If you are facing a sudden failure of graphics failure then I will suggest to follow the below steps:
- Clear the cookies and cache
- Also, reset the Zoom setting
- Disable hardware acceleration
- Disable extensions
Thanks for taking an interest Naheed.
-All cookies and cache cleared -Zoom uninstalled (seldom used on this machine anyway) -Don't know how to disable hardware acceleration - problem is only experienced with Firefox. Duckduckgo seems to perform ok on a few sample sites -Didn't think Firefox uses extensions - are add-ons the same thing? I don't think I have any installed.
So I'm afraid I still have a useless Firefox - but only on this device. It's working fine on an Android phone and a Windows laptop. Very odd.
I'd be glad to sort it out and happy to try any (reasonable!!) suggestions for doing so
Is the problem the same as described here?
Follow here: https://support.mozilla.org/en-US/questions/1333248
Exactly the same problem Sinsang. Thanks for spotting the similarity. I'm running FF Build 88.1.1. On a reload, first FF crashed and now it is failing to resolve any graphics or text in the browser window. One site I attempted to access has thrown up:
I can't read it because the text is replaced by lines of grey or black rectangles but this might help the good folk at Mozilla track down the cause of the problem which, like all others reported, appears to have happened suddenly in the last few days to previously long-term stable devices.
If you open the Android Settings app and select Applications, clear the cache (not data!) from Firefox for Android and other apps on your device. Restart your device and you should find it is resolved.
Thanks for the response Seburo.
Sadly there is no change.
- Clearing the cache of each app individually (tedious for a lot of apps)
- Using the "my files" app to clear the caches
- Cleared caches with "my files", uninstalled FF, Power off, wait power on reinstall FF; check caches and find 190Mb so cleared again, started FF tried Google and a known stable site but still the same unresolved presentation.
I am running FF 88.1.1 (build 2015804889) on a Samsung Galaxy Tab S2 under Android 5.0.2. The loss of resolution in Firefox happened overnight. I had not visited any unusual websites or changed my useage habits in any way. I can only guess that there was an automatic overnight update that has caused this incompatibility. Note that othe web browsers contiue to behave perfectly normally. I don't think this is a hardware or firmware problem but that it is very specific to FF.
Same here, although with the difference that, in the meantime, I tried Firefox 86 and it does not show the problem. The current releases of Beta, Nightly and Klar, on the other hand, do.
After removing 86, clearing the caches, rebooting and installing 88, the problem is back. And since it's not just the two of us, and the others have the same problem at the same time, I'd say this is a bug introduced with this week's release of 88, maybe in connection with Android 5 only.
Interesting. Thank you.
I had been wondering about rolling back to an earlier release to check for exactly the same thing but don't know how! With evidence like this maybe the folks at Mozilla can be persuaded to check back over their code for some unintentional incompatibility.
Just to compare notes. I have seen your response on the webrender.all and confirm your experience with about.config.
However, I have managed to access the information on my Galaxy A3 phone running Android 8.0.0, which is having no problems. Had to upload FF Nightly and go to debug to do so. Webrender.all appears not to be enabled. I presume this to be the case in all instances of FF88.1.1.
Thanks for prodding this one along. Resolution would be good.
Filed this as a bug with Mozilla: https://github.com/mozilla-mobile/fenix/issues/19230
I like to thumbdown
mmp144 is soo good always finding a problem
Not sure whether this is a weak compliment (a rarity for me) or an even weaker attempt at trolling (my first ever!). Whichever, Henricuz would be hard pressed to find any evidence to back up his statement and neither possibility makes any contribution to a careful attempt to document and find the solution for a software breakdown which is likely to affect many more Firefox users than the few of us who have been lucky enough to find our way to this intelligent and well run forum. I will not be responding to any more similar posts from this contributor and any more unhelpful posts will be referred for moderation.
The problem has apparently been identified as a driver issue in Android 5 with Mali T graphics. Should be fixed in Firefox 88.1.2.
Thanks to all involved. I look forward to being able to use FF as my prime browser very soon.
Just a quick note to confirm that this (as mentioned above) should be fixed in a forthcoming update.
As of yesterday evening everything is functioning perfectly. Release 8.1.2 has done its stuff. I'm very impressed by and grateful for the speed and effectiveness with which the bug was picked up and diagnosed and the fix disseminated. Thanks and congratulations to all involved.