X
Thinta lapha ukuze uye kuveshini yamakhalekhukhwini kusayithi.

Isithangami Sabeseki

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

57.0.1 unuseable

Kuphostiwe

Disallowing accessabilty access fixed problems for 57 which initially made firefox unuseable and eventually even full computer. Today Firefox upgraded to 57.0.1 and all problems are back. https://sourceforge.net/speedtest/ shows upload and DL speeds are decreased about 20%, but the real kickers are latency which increases about 10 to 100fold, from 16ms to 223 and then 1236ms, and packet loss consistently at 4 to 10%. After left open a while the firefox processes use up 100% of disk resources and whole computer becomes unuseable. Quitting and restarting firefox improve this but even at fresh restart, speedtest shows these awful latency and packet loss results immediately. Quitting firefox and same speedtest w Chrome I get latency 26ms, packet loss 0%, DL and UL about 20% faster. I reposted this on a few similar threads regarding the 57 problems but have been told to start a new thread. I am running Win8 and this is strictly a problem with firefox, no other apps, browsers etc. Since UL and DL speeds are still not bad I think the consistent very high packet loss, plus the numerous firefox processes which increase system resource use after perhaps a few hours to 100%, are current main problems.

Disallowing accessabilty access fixed problems for 57 which initially made firefox unuseable and eventually even full computer. Today Firefox upgraded to 57.0.1 and all problems are back. https://sourceforge.net/speedtest/ shows upload and DL speeds are decreased about 20%, but the real kickers are latency which increases about 10 to 100fold, from 16ms to 223 and then 1236ms, and packet loss consistently at 4 to 10%. After left open a while the firefox processes use up 100% of disk resources and whole computer becomes unuseable. Quitting and restarting firefox improve this but even at fresh restart, speedtest shows these awful latency and packet loss results immediately. Quitting firefox and same speedtest w Chrome I get latency 26ms, packet loss 0%, DL and UL about 20% faster. I reposted this on a few similar threads regarding the 57 problems but have been told to start a new thread. I am running Win8 and this is strictly a problem with firefox, no other apps, browsers etc. Since UL and DL speeds are still not bad I think the consistent very high packet loss, plus the numerous firefox processes which increase system resource use after perhaps a few hours to 100%, are current main problems.

Eminye Imininingwane Yohlelo

Fakela amapulagi

  • Shockwave Flash 27.0 r0

Isisebenziso

  • I-ejenti Engumsebenzisi: Mozilla/5.0 (Windows NT 6.2; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0

Eminye Imininingwane

Shadow110 1072 izisombululo 14836 izimpendulo
Kuphostiwe

Please : https://support.mozilla.org/en-US/kb/export-firefox-bookmarks-to-backup-or-transfer and https://support.mozilla.org/en-US/kb/back-and-restore-information-firefox-profiles then https://support.mozilla.org/en-US/kb/refresh-firefox-reset-add-ons-and-settings TEST....... If no issues then Extensions which need to be added back in 1 at a time and tested ..... Or it is your Profile : Make a new one and test ...: https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles

Can also reduce the processes  : Go the Menu then Tools --> Options --> Performance and untick everything. change the recommended size lower then see how it runs. Note: 0 = No Multi-proccesor = slow again. Hardware Acceleration might have also been a issue so turn it off. Run it later and see as you turn things back on and test it, and again. Restart Firefox after making these changes please.

Please let us know if this solved your issue or if need further assistance.

Please : https://support.mozilla.org/en-US/kb/export-firefox-bookmarks-to-backup-or-transfer and https://support.mozilla.org/en-US/kb/back-and-restore-information-firefox-profiles then https://support.mozilla.org/en-US/kb/refresh-firefox-reset-add-ons-and-settings TEST....... If no issues then Extensions which need to be added back in 1 at a time and tested ..... Or it is your Profile : Make a new one and test ...: https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles Can also reduce the processes : Go the Menu then Tools --> Options --> Performance and untick everything. change the recommended size lower then see how it runs. Note: 0 = No Multi-proccesor = slow again. Hardware Acceleration might have also been a issue so turn it off. Run it later and see as you turn things back on and test it, and again. Restart Firefox after making these changes please. Please let us know if this solved your issue or if need further assistance.

Okulungisiwe ngu Shadow110

Impendulo Ewusizo

I basically went through all these steps last week for 57 problems, which were quite a hassle and did nothing. 57 problem was then solved with accessability option. Please note that all mozilla's early responses telling users to go through all these steps and put the burden on users were all for nothing, and so far as all the similiar threads I monitored, were solved for almost everyone by disabling firefox accessability access,

But now everything is back. BTW this time reverting to early version of firefox didn't solve the problems temporarily, like 10 days ago it did [solved computer resources but not packet loss issues which rose to 18%]. Someone suggested disabling ublock which had no effect for me. I guess firefox has become unuseable for me and I have to export my bookmarks and move to chrome. I'll try to monitor threads occasionally and see if anyone comes up with anything more .

I basically went through all these steps last week for 57 problems, which were quite a hassle and did nothing. 57 problem was then solved with accessability option. Please note that all mozilla's early responses telling users to go through all these steps and put the burden on users were all for nothing, and so far as all the similiar threads I monitored, were solved for almost everyone by disabling firefox accessability access, But now everything is back. BTW this time reverting to early version of firefox didn't solve the problems temporarily, like 10 days ago it did [solved computer resources but not packet loss issues which rose to 18%]. Someone suggested disabling ublock which had no effect for me. I guess firefox has become unuseable for me and I have to export my bookmarks and move to chrome. I'll try to monitor threads occasionally and see if anyone comes up with anything more .

Okulungisiwe ngu bravedog

Shadow110 1072 izisombululo 14836 izimpendulo
Kuphostiwe

Going back : unfortunately 56.0.2 and below is no longer safe to use for every day use do to secuity issues, but 52.5.0 ESR is. It will continue to get security updates until May 2018, and you can download and install it from this page: https://www.mozilla.org/en-US/firefox/organizations/all/ Note : Legacy Extensions will be deleted or removed in any version update after May 2018.

You should make a backup of your Profile before going back and just because: https://support.mozilla.org/en-US/kb/back-and-restore-information-firefox-profiles

Please let us know if this solved your issue or if need further assistance.

Going back : unfortunately 56.0.2 and below is no longer safe to use for every day use do to secuity issues, but 52.5.0 ESR is. It will continue to get security updates until May 2018, and you can download and install it from this page: https://www.mozilla.org/en-US/firefox/organizations/all/ <b>Note : Legacy Extensions will be deleted or removed in any version update after May 2018</b>. You should make a backup of your Profile before going back and just because: https://support.mozilla.org/en-US/kb/back-and-restore-information-firefox-profiles Please let us know if this solved your issue or if need further assistance.

Umnikazi wombuzo

Tried 57.0.2, packet loss continues at 5%, latency down to 64 though

Tried 57.0.2, packet loss continues at 5%, latency down to 64 though
Shadow110 1072 izisombululo 14836 izimpendulo
Kuphostiwe

Correct Accessibility was the issue. 57.0.1 was the fix 57.02 fix issue with Profiles. cutting in 1/2 the processors allowed to be used is not the same thing .

You could try this please : Go the 3 Bar Menu then Options --> General --> Performance and untick everything. change the recommended size lower then see how it runs. Note: 0 = No Multiprocessor = slow again. Try 2 Restart Firefox after making these changes please.

58 is almost ready for release, it brings Multi-Thread Support.

Please let us know if this solved your issue or if need further assistance

Correct Accessibility was the issue. 57.0.1 was the fix 57.02 fix issue with Profiles. cutting in 1/2 the processors allowed to be used is not the same thing . You could try this please : Go the 3 Bar Menu then Options --> General --> Performance and untick everything. change the recommended size lower then see how it runs. Note: 0 = No Multiprocessor = slow again. Try 2 Restart Firefox after making these changes please. 58 is almost ready for release, it brings Multi-Thread Support. Please let us know if this solved your issue or if need further assistance

Umnikazi wombuzo

Thanks, this may have helped a little as it's the 1st time since this thread started latency was under 50 [ to 47], packet loss 3% which is down, but any packet loss is unacceptable, staying w Chrome for now, I'll continue to monitor for other ideas/updates. Too bad, Firefox has been my default browser for years. Getting used to Chrome. Also confirming w Chrome latency always below 50 [today 37] and always incl today 0% packet loss. This is definitely a FF issue.

Thanks, this may have helped a little as it's the 1st time since this thread started latency was under 50 [ to 47], packet loss 3% which is down, but any packet loss is unacceptable, staying w Chrome for now, I'll continue to monitor for other ideas/updates. Too bad, Firefox has been my default browser for years. Getting used to Chrome. Also confirming w Chrome latency always below 50 [today 37] and always incl today 0% packet loss. This is definitely a FF issue.

Okulungisiwe ngu bravedog

Tonnes
  • Locale Leader
246 izisombululo 1454 izimpendulo
Kuphostiwe

I think packet loss should not occur at all - not with any browser - if proven your internet connection is stable, either on the command prompt in your OS or by any tool. Speaking of, how did you test this, on a website?

Hence and moreover, did you check Firefox’s connection settings? Chances are they are set to use a system proxy (which happens by default for new profiles) that may not exist, be set incorrectly, or modified for some reason, even up to malware. Try setting "No proxy" instead unless you need one.

Fwiw, I can get Firefox into a state it doesn’t work smoothly (e.g. by opening too many tabs, web pages or add-ons causing issues, or by simply overloading the system by running it simultaneously with one or two instances of Firefox Nightly), but that never causes packet loss as far as I know. Therefor I assume fiddling with multi-process may help a bit, but not solve the actual issue.

Have you actually tested with a new profile as suggested, and do you have any security software installed (which is known to possibly cause issues with Firefox whereas it may not for other browsers), including additional software and features such as MalwareByte Anti Exploit? For the latter, did you restart Windows in Safe mode with networking enabled in order to quickly rule that out?

If you want to prove it’s Firefox being at fault as of version 57 and are sure the connection settings, proxy itself, add-ons or other profile related settings and security software are not an issue, you should definitely create a new profile beforehand for testing, set Firefox to *not* update itself in that profile, run a Nightly build either from here or from a zip file from its download repository, and use that test profile both in 57.0.2 and the Nightly, and even an older 56 (for that, you should be able to rename the .exe to include .zip and unzip the /core folder for a temporary install into a folder). That should provide you with any real evidence for it and may help others and developers.

I think packet loss should not occur at all - not with any browser - if proven your internet connection is stable, either on the command prompt in your OS or by any tool. Speaking of, how did you test this, on a website? Hence and moreover, did you check Firefox’s [[Connection settings in Firefox|connection settings]]? Chances are they are set to use a system proxy (which happens by default for new profiles) that may not exist, be set incorrectly, or modified for some reason, even up to malware. Try setting "No proxy" instead unless you need one. Fwiw, I can get Firefox into a state it doesn’t work smoothly (e.g. by opening too many tabs, web pages or add-ons causing issues, or by simply overloading the system by running it simultaneously with one or two instances of Firefox Nightly), but that never causes packet loss as far as I know. Therefor I assume fiddling with multi-process may help a bit, but not solve the actual issue. Have you actually tested with a new profile as suggested, and do you have any security software installed (which is known to possibly cause issues with Firefox whereas it may not for other browsers), including additional software and features such as MalwareByte Anti Exploit? For the latter, did you restart Windows in Safe mode with networking enabled in order to quickly rule that out? If you want to prove it’s Firefox being at fault as of version 57 and are sure the connection settings, proxy itself, add-ons or other profile related settings and security software are not an issue, you should definitely create a new profile beforehand for testing, set Firefox to *not* update itself in that profile, run a Nightly build either from [https://www.mozilla.org/en-US/firefox/channel/desktop/ here] or from a zip file from its [https://archive.mozilla.org/pub/firefox/nightly/latest-mozilla-central/ download repository], and use that test profile both in 57.0.2 and the Nightly, and even an [https://archive.mozilla.org/pub/firefox/releases/56.0.2/win64/en-US/ older 56] (for that, you should be able to rename the .exe to include .zip and unzip the /core folder for a temporary install into a folder). That should provide you with any real evidence for it and may help others and developers.

Umnikazi wombuzo

I am using https://sourceforge.net/speedtest/

Every time I use this with Firefox I get packet loss between 3-15%. Every time I close Firefox and try this with Chrome I get 0% packet loss. Therefore this is not an internet connection issue - until Firefox is opened.

As stated clearly in my 3rd post in this thread, 12/2, "I basically went through all these steps last week for 57 problems, which were quite a hassle and did nothing. " In addition today as there's the new update, besides trying the Settings suggestion, again set to New Profile. results remain the same. I also confirmed all extensions and addons are disabled.

These test results, if it wasn't clear, appear immediately upon opening Firefox, consistently, including packet loss. They aren't a matter of open a long time, many tabs, etc, though if left open a few hours, problems increase and the whole computer becomes unworkable and it becomes necessary to force-quit.

While I don't see this thread as trying t prove anything whatsoever, the simple fact that a dozen speedtests comparing Firefox and Chrome results, ALWAYS shows zero packet loss with Chrome and ALWAYS 3-15% packet loss with Firefox, does establish that Firefox [presumably in interaction with my specific system, but not due to my specific settings - not that setting alteration might not remedy the problems] - is causing the problems including packet loss and increased latency.

I do have AVG security software installed. Since it's preferable to abandon Firefox than security software, I am not testing if this is the incompatability, except that I did restart Firefox in Safe Mode which still shows the latency and packet loss problems, yes; alsor, I haven't changed my security software in years and if this is somehow the conflict in spite of Safe Mode test, it didn't exist prior to Firefox 57 and is still a new problem and a Firefox problem IMO.

I don't like creating a New Profile, which I've done in the past and regretted. When the accessability access problems arose before they'd been identified, I did install an earlier version of FF turning off updates which worked then but now doesn't.

I tried setting to No Proxy as you suggested. Retesting, get latency 70ms, packet loss 6%.

I am using https://sourceforge.net/speedtest/ Every time I use this with Firefox I get packet loss between 3-15%. Every time I close Firefox and try this with Chrome I get 0% packet loss. Therefore this is not an internet connection issue - until Firefox is opened. As stated clearly in my 3rd post in this thread, 12/2, "I basically went through all these steps last week for 57 problems, which were quite a hassle and did nothing. " In addition today as there's the new update, besides trying the Settings suggestion, again set to New Profile. results remain the same. I also confirmed all extensions and addons are disabled. These test results, if it wasn't clear, appear immediately upon opening Firefox, consistently, including packet loss. They aren't a matter of open a long time, many tabs, etc, though if left open a few hours, problems increase and the whole computer becomes unworkable and it becomes necessary to force-quit. While I don't see this thread as trying t prove anything whatsoever, the simple fact that a dozen speedtests comparing Firefox and Chrome results, ALWAYS shows zero packet loss with Chrome and ALWAYS 3-15% packet loss with Firefox, does establish that Firefox [presumably in interaction with my specific system, but not due to my specific settings - not that setting alteration might not remedy the problems] - is causing the problems including packet loss and increased latency. I do have AVG security software installed. Since it's preferable to abandon Firefox than security software, I am not testing if this is the incompatability, except that I did restart Firefox in Safe Mode which still shows the latency and packet loss problems, yes; alsor, I haven't changed my security software in years and if this is somehow the conflict in spite of Safe Mode test, it didn't exist prior to Firefox 57 and is still a new problem and a Firefox problem IMO. I don't like creating a New Profile, which I've done in the past and regretted. When the accessability access problems arose before they'd been identified, I did install an earlier version of FF turning off updates which worked then but now doesn't. I tried setting to No Proxy as you suggested. Retesting, get latency 70ms, packet loss 6%.
Tonnes
  • Locale Leader
246 izisombululo 1454 izimpendulo
Kuphostiwe

Impendulo Ewusizo

I’m sorry but apart from your last sentence, I think you wasted some time.

Your references to the 12/2 post say nothing and clearly indicate you didn’t notice I gave remaining steps not covered in previously quoted articles. Please do not try to decide for yourself what helpers’ suggestions are good or not, nor to be stubborn in following required troubleshooting steps we can give and are limited to, and do not assume creating an additional test profile is a hassle or just something you don’t like where you appear to have referred to a previous Refresh that you may have had a bad experience with. You can set up and choose from 20 or more profiles within a minute without touching your current setup, and it would take a few minutes at most for unzipping and running other versions. I did not tell you to abandon your security software either (which according to some is not even required these days when being hardware-protected) but to disable it temporarily by telling Windows not to let it interfere using its Safe Mode rather than using the unreliable method of disabling it in its settings. You really should try all that before claiming "Firefox definitely has an issue".

As for what you wrote more, suffering packet loss each time when starting Firefox makes more sense than issues arising after a while, which may be a separate memory related issue I will not deny that may exist, but this is about your connection. Also, writing about the previous version now suffering the issue too merely indicates security software is related, as opposed to just declaring 57+ has an issue, and you should understand that. Key is Firefox handles connections differently than most browsers on the market do today (leading to more issues with regard to some additional and related software and less priority for them to fix in some cases), so you should take that into account. We have seen plenty of issues related to certificates or SSL scanning to name a few, often reflecting in issues occurring in Firefox and perhaps a few other browsers only. One flaky recent update would be enough to cause your issue, so to speak.

Any developer tools included that you could troubleshoot with did not even come up in this question, though I think the other steps could solve it sooner.

Believe me, if we were allowed to log in to user systems remotely either because of impatient or even reluctant users, we would have done so, but text is the way to use and users need to take the steps. You are not the first user asking for help here but refusing to act the way they should or getting deluded by thinking "its not their security software that’s been working for years" or "other browsers have no issue" and blaming Firefox without proper investigation, awaiting the right answer by yet another helper if that matters. You were given the steps to rule out culprits and to proof there is a real issue or not and which always worked for me. If you choose not to follow them, I’m afraid no-one can or is still willing to help you out here, your question will remain unsolved, and in case there really is an issue, you won’t help others either (assumingly at least 4 others at this point), so visiting a computer repair shop would be what’s left. You just can’t expect us to reply with the perfect solution otherwise, and you should know. But choice is choice, and we encourage it. ;)

So please re-read and try, and if not, good luck.

I’m sorry but apart from your last sentence, I think you wasted some time. Your references to the 12/2 post say nothing and clearly indicate you didn’t notice I gave remaining steps not covered in previously quoted articles. Please do not try to decide for yourself what helpers’ suggestions are good or not, nor to be stubborn in following required troubleshooting steps we can give and are limited to, and do not assume creating an ''additional test profile'' is a hassle or just something you don’t like where you appear to have referred to a previous Refresh that you may have had a bad experience with. You can set up and choose from 20 or more [[Use the Profile Manager to create and remove Firefox profiles|profiles]] within a minute without touching your current setup, and it would take a few minutes at most for unzipping and running other versions. I did not tell you to abandon your security software either (which according to some is not even required these days when being hardware-protected) but to disable it temporarily by telling Windows not to let it interfere using its Safe Mode rather than using the unreliable method of disabling it in its settings. You really should try all that before claiming "Firefox definitely has an issue". As for what you wrote more, suffering packet loss each time when starting Firefox makes more sense than issues arising after a while, which may be a separate memory related issue I will not deny that may exist, but this is about your connection. Also, writing about the previous version now suffering the issue too merely indicates security software is related, as opposed to just declaring 57+ has an issue, and you should understand that. Key is Firefox handles connections differently than most browsers on the market do today (leading to more issues with regard to some additional and related software and less priority for them to fix in some cases), so you should take that into account. We have seen plenty of issues related to certificates or SSL scanning to name a few, often reflecting in issues occurring in Firefox and perhaps a few other browsers only. One flaky recent update would be enough to cause your issue, so to speak. Any developer tools included that you could troubleshoot with did not even come up in this question, though I think the other steps could solve it sooner. Believe me, if we were allowed to log in to user systems remotely either because of impatient or even reluctant users, we would have done so, but text is the way to use and users need to take the steps. You are not the first user asking for help here but refusing to act the way they should or getting deluded by thinking "its not their security software that’s been working for years" or "other browsers have no issue" and blaming Firefox without proper investigation, awaiting the right answer by yet another helper if that matters. You were given the steps to rule out culprits and to proof there is a real issue or not and which always worked for me. If you choose not to follow them, I’m afraid no-one can or is still willing to help you out here, your question will remain unsolved, and in case there really is an issue, you won’t help others either (assumingly at least 4 others at this point), so visiting a computer repair shop would be what’s left. You just can’t expect us to reply with the perfect solution otherwise, and you should know. But choice is choice, and we encourage it. ;) So please re-read and try, and if not, good luck.

Umnikazi wombuzo

Here are specific steps I went to or direct responses to your earlier post 1]reset Firefox connectionsettings as suggested 2]clarified issues appear immediately, not just over time or w many tabs 3]started Firefox in safe Mode 4]again reset Firefox to defaults 5]confirmed all extensions and addons are disabled 6]confirmed no packet loss when Firefox not open 7] gave specifics of how I was testing packet loss

Here are the only steps I didn't go through 1]new profile 2]disable security software

Your characterization that I refused to do anything is off, although I didn't do completely everything you suggested your claim my only step taken was #1 above is wrong.

No, I don't need a computer repair shop. My computer is working great - when Firefox isn't loaded.

Here are specific steps I went to or direct responses to your earlier post 1]reset Firefox connectionsettings as suggested 2]clarified issues appear immediately, not just over time or w many tabs 3]started Firefox in safe Mode 4]again reset Firefox to defaults 5]confirmed all extensions and addons are disabled 6]confirmed no packet loss when Firefox not open 7] gave specifics of how I was testing packet loss Here are the only steps I didn't go through 1]new profile 2]disable security software Your characterization that I refused to do anything is off, although I didn't do completely everything you suggested your claim my only step taken was #1 above is wrong. No, I don't need a computer repair shop. My computer is working great - when Firefox isn't loaded.

Okulungisiwe ngu bravedog

Umnikazi wombuzo

Updated to 57.0.4, https://sourceforge.net/speedtest/ shows latency 88ms,packet loss 7%; with Chrome [without closing Firefox] latency 42ms, packet loss 0

Updated to 57.0.4, https://sourceforge.net/speedtest/ shows latency 88ms,packet loss 7%; with Chrome [without closing Firefox] latency 42ms, packet loss 0
Shadow110 1072 izisombululo 14836 izimpendulo
Kuphostiwe

uninstall Firefox. Then Delete the Mozilla Firefox Folders in C:\Program Files and C:\Program Files(x86) Then restart system. Then run Windows Disk Cleanup. (Note: This should be Pinned and run Weekly, If never done below expect 10's of gig's) Then run it again and click the button that says Cleanup System Files. Note: your Firefox Profile is saved. But you should make a back up before you do :

Reinstall with Current Release Firefox 57.0.4 with a Full Version Installer

Try : http://www.speedtest.net/

Please let us know if this solved your issue or if need further assistance.

uninstall Firefox. Then Delete the Mozilla Firefox Folders in C:\Program Files and C:\Program Files(x86) Then restart system. Then run Windows Disk Cleanup. (Note: This should be Pinned and run Weekly, If never done below expect 10's of gig's) Then run it again and click the button that says Cleanup System Files. Note: your Firefox Profile is saved. But you should make a back up before you do : *https://support.mozilla.org/en-US/kb/back-and-restore-information-firefox-profiles *https://support.mozilla.org/en-US/kb/export-firefox-bookmarks-to-backup-or-transfer Reinstall with Current Release Firefox 57.0.4 with a Full Version Installer *https://www.mozilla.org/firefox/all/ Try : http://www.speedtest.net/ Please let us know if this solved your issue or if need further assistance.

Umnikazi wombuzo

Uninstalled FF, deleted FF folders in computer, restarted computer, ran disk cleanup, then again clicking Clean System Files, reinstalled FF. Same issues. https://sourceforge.net/speedtest/ shows latency 54ms,packet loss 4.5%; with Chrome [without closing Firefox] latency 48ms, packet loss 0

Uninstalled FF, deleted FF folders in computer, restarted computer, ran disk cleanup, then again clicking Clean System Files, reinstalled FF. Same issues. https://sourceforge.net/speedtest/ shows latency 54ms,packet loss 4.5%; with Chrome [without closing Firefox] latency 48ms, packet loss 0

Umnikazi wombuzo

http://beta.speedtest.net/ FF however shows ping 7ms. This site does not measure packet loss.

http://beta.speedtest.net/ FF however shows ping 7ms. This site does not measure packet loss.
Shadow110 1072 izisombululo 14836 izimpendulo
Kuphostiwe

It is possible that the internet and time and ISP bandwidth has passed your Network Cards Capability. Please go to Device Manager and Click Network Card and get the info for the card. Google the card and maker and see what the specs are on the card. Also see if the have a updated driver for you.

It is possible that the internet and time and ISP bandwidth has passed your Network Cards Capability. Please go to Device Manager and Click Network Card and get the info for the card. Google the card and maker and see what the specs are on the card. Also see if the have a updated driver for you.

Umnikazi wombuzo

Please note speed test results in above posts for Chrome browser. For Chrome and IE, these issues do not exist. There is zero packet loss and consistent latency < 50ms. These problems exist only for Firefox. Therefore this is not a network or bandwidth issue but a conflict between FF - only since 14 - and something else on my system [presumably] - not an extension as I've disabled all.

Please note speed test results in above posts for Chrome browser. For Chrome and IE, these issues do not exist. There is zero packet loss and consistent latency < 50ms. These problems exist only for Firefox. Therefore this is not a network or bandwidth issue but a conflict between FF - only since 14 - and something else on my system [presumably] - not an extension as I've disabled all.
Shadow110 1072 izisombululo 14836 izimpendulo
Kuphostiwe
Firefox Based Alternatives https://www.palemoon.org/ https://www.waterfoxproject.org/ https://www.comodo.com/home/browsers-toolbars/icedragon-browser.php https://www.gnu.org/software/icecat/ www.cometbird.com/ I run this as a 2nd browser https://www.seamonkey-project.org/ is like Netscape with mail and HTML Editor. www.cometbird.com/ https://www.torproject.org/projects/torbrowser.html.en https://vivaldi.com/?lang=en

Umnikazi wombuzo

Interesting, thanks!

Since FF went south for me I've been using Chrome,seems to be working well and I've gotten adjusted to it.

I'll continue to update FF in case it starts working for me again. Later

Interesting, thanks! Since FF went south for me I've been using Chrome,seems to be working well and I've gotten adjusted to it. I'll continue to update FF in case it starts working for me again. Later

Umnikazi wombuzo

tried 59.0.1 which for the 1st time since 57 shows some improvement with latency at 41ms the 1st time since 57 at an acceptable <50ms, and packet loss at 1%, still having any unacceptable, but in earlier versions was more like 5-10% so a real improvement

still using chrome,will keep checking back

tried 59.0.1 which for the 1st time since 57 shows some improvement with latency at 41ms the 1st time since 57 at an acceptable <50ms, and packet loss at 1%, still having any unacceptable, but in earlier versions was more like 5-10% so a real improvement still using chrome,will keep checking back
Shadow110 1072 izisombululo 14836 izimpendulo
Kuphostiwe

To submit suggestions for new or changed features, may I suggest: Feedback: https://qsurvey.mozilla.com/s3/FirefoxInput/ If you have a bug, file a bug report. https://bugzilla.mozilla.org/ Bug Writing Guidelines : https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines

To submit suggestions for new or changed features, may I suggest: Feedback: https://qsurvey.mozilla.com/s3/FirefoxInput/ If you have a bug, file a bug report. https://bugzilla.mozilla.org/ Bug Writing Guidelines : https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines