X
Tap here to go to the mobile version of the site.

منتدى الدعم

Firefox update 63.0.1 is "super" slow. Nothing in the fix suggestions works.

Posted

This has been an ongoing problem that started, first with update 63.0, and continues with update 63.0.1.

I have tried multiple fix suggestions, including the very disappointing "refresh Firefox" option. While that did nothing to cure the problem, it did wipe out every saved password. That, to be blunt, really ticked me off. It says this fix solution will keep our saved information, with no mention of erasing passwords.

Second, I changed the Network Settings as directed, from Use system proxy settings to auto-detect proxy settings for this network. I have been cautioned NOT to use the no proxy option, because it has a chance of rendering some websites unavailable. Not interested in messing up my browsing experience any worse than these recent Firefox updates have accomplished by themselves.

All these problems aside, my biggest disappointment is in the total lack of communication from Mozilla. While I value the Firefox ideology and the mission to provide a more private internet browsing experience, all this is worthless to me if my pages load at something akin to dial-up speeds.

At this juncture I have no choice but to use Google Chrome until someone can provide me with a workable solution, a solution that doesn't send me back to square one with all my saved Firefox information. If that is the only remedy, I might as well switch my default browser now and begin to re-acclimate myself to the changes.

Thanks.

This has been an ongoing problem that started, first with update 63.0, and continues with update 63.0.1. I have tried multiple fix suggestions, including the very disappointing "refresh Firefox" option. While that did nothing to cure the problem, it did wipe out every saved password. That, to be blunt, really ticked me off. It says this fix solution will keep our saved information, with no mention of erasing passwords. Second, I changed the Network Settings as directed, from Use system proxy settings to auto-detect proxy settings for this network. I have been cautioned NOT to use the no proxy option, because it has a chance of rendering some websites unavailable. Not interested in messing up my browsing experience any worse than these recent Firefox updates have accomplished by themselves. All these problems aside, my biggest disappointment is in the total lack of communication from Mozilla. While I value the Firefox ideology and the mission to provide a more private internet browsing experience, all this is worthless to me if my pages load at something akin to dial-up speeds. At this juncture I have no choice but to use Google Chrome until someone can provide me with a workable solution, a solution that doesn't send me back to square one with all my saved Firefox information. If that is the only remedy, I might as well switch my default browser now and begin to re-acclimate myself to the changes. Thanks.

Chosen solution

I did not need to utilize the Safe Mode suggestion.

Early on, I saw where changing the proxy settings "might" correct Firefox running slow. There were also some words of caution across the geek community in information I researched against altering how Firefox connects to the internet, (ie: proxy settings).

Today I had the time to dig deeper into this option and flipped back to "no proxy". Things have returned to normal, thank God. Sorry, not a big fan of the "Other Browsers".

My question at this juncture would be how, or why did the 63.0.1 Firefox update alter my connection settings? As I mentioned, I have been navigating around in cyberspace using Firefox as my primary browser, and never experienced an issue until now.

Thanks Fred McD for the suggestions. Just in case I have to revisit this problem in the future, I have logged some of your valuable links.

Hopefully I can consider this issue fixed and begin to browse on, again at 21st century speeds. Shoot, there were moments when I thought I heard the infamous dial tone it was so slow.

Thanks again.

Read this answer in context 0

Additional System Details

Application

  • Firefox 63.0.1
  • User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:63.0) Gecko/20100101 Firefox/63.0
  • Support URL: https://support.mozilla.org/1/firefox/63.0.1/WINNT/en-US/

Extensions

  • Adobe Acrobat 18.0.9 (web2pdfextension.17@acrobat.adobe.com) (Inactive)

Javascript

  • incrementalGCEnabled: True

Graphics

  • adapterDescription: Intel(R) G41 Express Chipset
  • adapterDescription2:
  • adapterDeviceID: 0x2e32
  • adapterDeviceID2:
  • adapterDrivers: igdumd64 igd10umd64 igdumdx32 igd10umd32
  • adapterDrivers2:
  • adapterRAM: Unknown
  • adapterRAM2:
  • adapterSubsysID: 2a8c103c
  • adapterSubsysID2:
  • adapterVendorID: 0x8086
  • adapterVendorID2:
  • clearTypeParameters: Gamma: 2.2 Pixel Structure: RGB
  • contentUsesTiling: True
  • crashGuards: []
  • direct2DEnabled: False
  • direct2DEnabledMessage: [u'blockedDriver']
  • directWriteEnabled: True
  • directWriteVersion: 6.2.9200.22164
  • driverDate: 10-15-2010
  • driverDate2:
  • driverVersion: 8.15.10.2226
  • driverVersion2:
  • featureLog: {u'fallbacks': [], u'features': [{u'status': u'available', u'description': u'Compositing', u'log': [{u'status': u'available', u'type': u'default'}], u'name': u'HW_COMPOSITING'}, {u'status': u'blacklisted', u'description': u'Direct3D11 Compositing', u'log': [{u'status': u'available', u'type': u'default'}, {u'status': u'blacklisted', u'message': u'#BLOCKLIST_FEATURE_FAILURE_BUG_1116812', u'type': u'env'}], u'name': u'D3D11_COMPOSITING'}, {u'status': u'unavailable', u'description': u'Direct2D', u'log': [{u'status': u'unavailable', u'message': u'Direct2D requires Direct3D 11 compositing', u'type': u'default'}], u'name': u'DIRECT2D'}, {u'status': u'disabled', u'description': u'Direct3D11 hardware ANGLE', u'log': [{u'status': u'unavailable', u'message': u'D3D11 compositing is disabled', u'type': u'default'}, {u'status': u'disabled', u'message': u'D3D11 compositing is disabled', u'type': u'env'}], u'name': u'D3D11_HW_ANGLE'}, {u'status': u'available', u'description': u'GPU Process', u'log': [{u'status': u'available', u'type': u'default'}], u'name': u'GPU_PROCESS'}, {u'status': u'unavailable', u'description': u'WebRender', u'log': [{u'status': u'opt-in', u'message': u'WebRender is an opt-in feature', u'type': u'default'}, {u'status': u'unavailable', u'message': u'ANGLE is disabled', u'type': u'runtime'}], u'name': u'WEBRENDER'}, {u'status': u'blocked', u'description': u'WebRender qualified', u'log': [{u'status': u'available', u'type': u'default'}, {u'status': u'blocked', u'message': u'No qualified hardware', u'type': u'env'}], u'name': u'WEBRENDER_QUALIFIED'}, {u'status': u'available', u'description': u'Off Main Thread Painting', u'log': [{u'status': u'available', u'type': u'default'}], u'name': u'OMTP'}]}
  • info: {u'AzureContentBackend (UI Process)': u'skia', u'AzureCanvasBackend (UI Process)': u'skia', u'ApzWheelInput': 1, u'ApzDragInput': 1, u'ApzKeyboardInput': 1, u'AzureFallbackCanvasBackend (UI Process)': u'cairo', u'ApzAutoscrollInput': 1, u'AzureCanvasAccelerated': 0, u'AzureCanvasBackend': u'skia', u'AzureContentBackend': u'skia'}
  • isGPU2Active: False
  • numAcceleratedWindows: 0
  • numAcceleratedWindowsMessage: [u'']
  • numTotalWindows: 1
  • offMainThreadPaintEnabled: True
  • offMainThreadPaintWorkerCount: 1
  • usesTiling: False
  • webgl1DriverExtensions: GL_ANGLE_client_arrays GL_ANGLE_explicit_context GL_ANGLE_explicit_context_gles1 GL_ANGLE_framebuffer_blit GL_ANGLE_framebuffer_multisample GL_ANGLE_instanced_arrays GL_ANGLE_lossy_etc_decode GL_ANGLE_pack_reverse_row_order GL_ANGLE_program_cache_control GL_ANGLE_request_extension GL_ANGLE_robust_client_memory GL_ANGLE_texture_compression_dxt3 GL_ANGLE_texture_compression_dxt5 GL_ANGLE_texture_usage GL_ANGLE_translated_shader_source GL_CHROMIUM_bind_generates_resource GL_CHROMIUM_bind_uniform_location GL_CHROMIUM_color_buffer_float_rgb GL_CHROMIUM_color_buffer_float_rgba GL_CHROMIUM_copy_compressed_texture GL_CHROMIUM_copy_texture GL_CHROMIUM_sync_query GL_EXT_blend_minmax GL_EXT_color_buffer_half_float GL_EXT_debug_marker GL_EXT_discard_framebuffer GL_EXT_disjoint_timer_query GL_EXT_draw_buffers GL_EXT_frag_depth GL_EXT_map_buffer_range GL_EXT_occlusion_query_boolean GL_EXT_read_format_bgra GL_EXT_robustness GL_EXT_sRGB GL_EXT_shader_texture_lod GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_s3tc_srgb GL_EXT_texture_filter_anisotropic GL_EXT_texture_format_BGRA8888 GL_EXT_texture_storage GL_EXT_unpack_subimage GL_KHR_debug GL_KHR_robust_buffer_access_behavior GL_NV_EGL_stream_consumer_external GL_NV_fence GL_NV_pack_subimage GL_NV_pixel_buffer_object GL_OES_EGL_image GL_OES_EGL_image_external GL_OES_compressed_ETC1_RGB8_texture GL_OES_depth32 GL_OES_element_index_uint GL_OES_get_program_binary GL_OES_mapbuffer GL_OES_packed_depth_stencil GL_OES_rgb8_rgba8 GL_OES_standard_derivatives GL_OES_surfaceless_context GL_OES_texture_float GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_OES_texture_npot GL_OES_vertex_array_object OES_compressed_EAC_R11_signed_texture OES_compressed_EAC_R11_unsigned_texture OES_compressed_EAC_RG11_signed_texture OES_compressed_EAC_RG11_unsigned_texture OES_compressed_ETC2_RGB8_texture OES_compressed_ETC2_RGBA8_texture OES_compressed_ETC2_punchthroughA_RGBA8_texture OES_compressed_ETC2_punchthroughA_sRGB8_alpha_texture OES_compressed_ETC2_sRGB8_alpha8_texture OES_compressed_ETC2_sRGB8_texture
  • webgl1Extensions: ANGLE_instanced_arrays EXT_blend_minmax EXT_color_buffer_half_float EXT_frag_depth EXT_sRGB EXT_shader_texture_lod EXT_texture_filter_anisotropic EXT_disjoint_timer_query OES_element_index_uint OES_standard_derivatives OES_texture_float OES_texture_half_float OES_texture_half_float_linear OES_vertex_array_object WEBGL_color_buffer_float WEBGL_compressed_texture_s3tc WEBGL_compressed_texture_s3tc_srgb WEBGL_debug_renderer_info WEBGL_debug_shaders WEBGL_draw_buffers WEBGL_lose_context
  • webgl1Renderer: Google Inc. -- ANGLE (Intel(R) G41 Express Chipset Direct3D11 vs_4_0 ps_4_0)
  • webgl1Version: OpenGL ES 2.0 (ANGLE 2.1.0.ae3b5a6552ee)
  • webgl1WSIInfo: EGL_VENDOR: Google Inc. (adapter LUID: 0000000000009a85) EGL_VERSION: 1.4 (ANGLE 2.1.0.ae3b5a6552ee) EGL_EXTENSIONS: EGL_EXT_create_context_robustness EGL_ANGLE_d3d_share_handle_client_buffer EGL_ANGLE_d3d_texture_client_buffer EGL_ANGLE_surface_d3d_texture_2d_share_handle EGL_ANGLE_query_surface_pointer EGL_ANGLE_window_fixed_size EGL_ANGLE_keyed_mutex EGL_ANGLE_surface_orientation EGL_NV_post_sub_buffer EGL_KHR_create_context EGL_EXT_device_query EGL_KHR_image EGL_KHR_image_base EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_KHR_get_all_proc_addresses EGL_KHR_stream EGL_KHR_stream_consumer_gltexture EGL_NV_stream_consumer_gltexture_yuv EGL_ANGLE_flexible_surface_compatibility EGL_ANGLE_stream_producer_d3d_texture EGL_ANGLE_create_context_webgl_compatibility EGL_CHROMIUM_create_context_bind_generates_resource EGL_EXT_pixel_format_float EGL_KHR_surfaceless_context EGL_ANGLE_display_texture_share_group EGL_ANGLE_create_context_client_arrays EGL_ANGLE_program_cache_control EGL_ANGLE_robust_resource_initialization EGL_ANGLE_create_context_extensions_enabled EGL_EXTENSIONS(nullptr): EGL_EXT_client_extensions EGL_EXT_platform_base EGL_EXT_platform_device EGL_ANGLE_platform_angle EGL_ANGLE_platform_angle_d3d EGL_ANGLE_device_creation EGL_ANGLE_device_creation_d3d11 EGL_ANGLE_experimental_present_path EGL_KHR_client_get_all_proc_addresses EGL_ANGLE_explicit_context
  • webgl2DriverExtensions: -
  • webgl2Extensions: -
  • webgl2Renderer: WebGL creation failed: * tryANGLE * Exhausted GL driver options.
  • webgl2Version: -
  • webgl2WSIInfo: -
  • windowLayerManagerRemote: True
  • windowLayerManagerType: Basic
  • windowUsingAdvancedLayers: False

Modified Preferences

Misc

  • User JS: No
  • Accessibility: No
FredMcD
  • Top 10 Contributor
4248 solutions 59425 answers

ProfessorCNut said

including the very disappointing "refresh Firefox" option. While that did nothing to cure the problem, it did wipe out every saved password.

Refreshing Firefox {web link} is a LAST RESORT ! !

Refreshing Firefox -- easily fix most problems

If you're having problems with Firefox, refreshing it can help. The refresh feature fixes many issues by restoring Firefox to its factory default state while saving your essential information like bookmarks and open tabs. Everything else, like user settings and add-ons, are removed.


Note: The current profile is moved to a folder on your desktop. We will worry about it later.

''ProfessorCNut [[#question-1239357|said]]'' <blockquote> including the very disappointing "refresh Firefox" option. While that did nothing to cure the problem, it did wipe out every saved password. </blockquote> [https://support.mozilla.org/en-US/kb/refresh-firefox-reset-add-ons-and-settings Refreshing Firefox] {web link} is a '''LAST RESORT ! !''' Refreshing Firefox -- easily fix most problems If you're having problems with Firefox, refreshing it can help. The refresh feature fixes many issues by restoring Firefox to its factory default state while saving your essential information like bookmarks and open tabs. Everything else, like user settings and add-ons, are removed. Note: The current profile is moved to a folder on your desktop. We will worry about it later.
FredMcD
  • Top 10 Contributor
4248 solutions 59425 answers

Helpful Reply

Make sure you are not blocking content.

Start Firefox in Safe Mode {web link} by holding down the <Shift> (Mac=Options) key, and then starting Firefox.

A small dialog should appear. Click Start In Safe Mode (not Refresh). Is the problem still there?


One issue that seems more common lately is Firefox's Tracking Protection feature. When it is blocking content in a page, a shield icon will appear at the left end of the address bar next to the padlock icon. This article has more info on managing this feature: Tracking Protection {web link}

Make sure you are not blocking content. [https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode Start Firefox in Safe Mode] {web link} by holding down the '''<Shift> ''(Mac=Options)''''' key, and then starting Firefox. A small dialog should appear. Click '''Start In Safe Mode''' (not Refresh). Is the problem still there? --------------- One issue that seems more common lately is Firefox's Tracking Protection feature. When it is blocking content in a page, a shield icon will appear at the left end of the address bar next to the padlock icon. This article has more info on managing this feature: [https://support.mozilla.org/en-US/kb/tracking-protection Tracking Protection] {web link}

Question owner

Removed all the tracking protection features as well.

There is no evidence the shield icon ever appears on any of the websites. This slowness is inherent on every website, including the Mozzila help forum I am currently in.

Every website loads normally on Google Chrome, so the problem is obviously a Firefox issue. I have been a longtime user, and this new issue materialized with the download of updates 63.0 and 63.0.1.

I am not a developer, but what test evidence I can produce points directly at a problem with one or both of these updates. Nothing else has changed on anything I do.

Oh, and as for the refresh idea: Firefox will save these items:

   • Bookmarks
   • Browsing and download history
   • Passwords
   • Open windows and tabs
   • Cookies
   • Web form auto-fill information
   • Personal dictionary 

NOT! The refresh "last resort idea" wiped every saved password off the books.

Thanks for the attempts to help, but nothing as yet is changing the situation for the better. Certainly appears Chrome has a new/old customer returning, as begrudgingly as I accept that necessity.

I simply cannot justify the slow and frustrating performance of Firefox as my default browser much longer.

Thanks.

Removed all the tracking protection features as well. There is no evidence the shield icon ever appears on any of the websites. This slowness is inherent on every website, including the Mozzila help forum I am currently in. Every website loads normally on Google Chrome, so the problem is obviously a Firefox issue. I have been a longtime user, and this new issue materialized with the download of updates 63.0 and 63.0.1. I am not a developer, but what test evidence I can produce points directly at a problem with one or both of these updates. Nothing else has changed on anything I do. Oh, and as for the refresh idea: Firefox will save these items: • Bookmarks • Browsing and download history • Passwords • Open windows and tabs • Cookies • Web form auto-fill information • Personal dictionary NOT! The refresh "last resort idea" wiped every saved password off the books. Thanks for the attempts to help, but nothing as yet is changing the situation for the better. Certainly appears Chrome has a new/old customer returning, as begrudgingly as I accept that necessity. I simply cannot justify the slow and frustrating performance of Firefox as my default browser much longer. Thanks.
FredMcD
  • Top 10 Contributor
4248 solutions 59425 answers
Your original profile data should be safe. Do any of these links help? https://support.mozilla.org/kb/Firefox+is+already+running+but+is+not+responding https://support.mozilla.org/en-US/kb/firefox-slow-how-make-it-faster https://support.mozilla.org/en-US/kb/firefox-uses-too-many-cpu-resources-how-fix https://support.mozilla.org/en-US/kb/firefox-uses-too-much-memory-ram https://support.mozilla.org/en-US/kb/firefox-hangs-or-not-responding

Question owner

In response to your helpful suggestions, here is how I have attempted to address the problem.

1. https://support.mozilla.org/kb/Firefox+is+already+running+but+is+not+responding

• This has happened on one occasion. Opened Firefox as I have hundreds of times and nothing happened. Opened approximately 10 minutes later to my surprise. This phenomenon has not repeated other than that one time.

2. https://support.mozilla.org/en-US/kb/firefox-slow-how-make-it-faster

• This has been the link with suggestions that seem to just send me round in circles chasing my tail. As we progress further down your list of suggested links to fix the slowness, the problem seems to point back to something wrong with the 63.0.1 update. I have worked through no less than 4 of the suggestions from the above line, but no success.

3. https://support.mozilla.org/en-US/kb/firefox-uses-too-many-cpu-resources-how-fix

• Firefox appears to be using no additional resources than ever before. My concern would be, that when I compare the massive CPU hound Google Chrome with Firefox, the numbers are still FAR less for Firefox. However, Chrome is running normally and Firefox is at a snail's pace.

4. https://support.mozilla.org/en-US/kb/firefox-uses-too-much-memory-ram

• Same issue as the above suggestion. There has been no change in memory use.

5. https://support.mozilla.org/en-US/kb/firefox-hangs-or-not-responding

• Other than the monumental 10 minute delay opening, "hangs and slow" are the only things that point to this as a viable solution. Unfortunately, nothing suggested changes the speed of Firefox for the better.

I greatly appreciate these helpful tips, but unfortunately nothing is working as of yet. I have been forced to step over to that "other browser" until a solution is presented.

I am though, rather dismayed at the lack of communication from Mozilla. Seems they would be more concerned with a obvious issue with one of their updates.

Thanks Fred for the efforts to help.

In response to your helpful suggestions, here is how I have attempted to address the problem. 1. https://support.mozilla.org/kb/Firefox+is+already+running+but+is+not+responding • This has happened on one occasion. Opened Firefox as I have hundreds of times and nothing happened. Opened approximately 10 minutes later to my surprise. This phenomenon has not repeated other than that one time. 2. https://support.mozilla.org/en-US/kb/firefox-slow-how-make-it-faster • This has been the link with suggestions that seem to just send me round in circles chasing my tail. As we progress further down your list of suggested links to fix the slowness, the problem seems to point back to something wrong with the 63.0.1 update. I have worked through no less than 4 of the suggestions from the above line, but no success. 3. https://support.mozilla.org/en-US/kb/firefox-uses-too-many-cpu-resources-how-fix • Firefox appears to be using no additional resources than ever before. My concern would be, that when I compare the massive CPU hound Google Chrome with Firefox, the numbers are still FAR less for Firefox. However, Chrome is running normally and Firefox is at a snail's pace. 4. https://support.mozilla.org/en-US/kb/firefox-uses-too-much-memory-ram • Same issue as the above suggestion. There has been no change in memory use. 5. https://support.mozilla.org/en-US/kb/firefox-hangs-or-not-responding • Other than the monumental 10 minute delay opening, "hangs and slow" are the only things that point to this as a viable solution. Unfortunately, nothing suggested changes the speed of Firefox for the better. I greatly appreciate these helpful tips, but unfortunately nothing is working as of yet. I have been forced to step over to that "other browser" until a solution is presented. I am though, rather dismayed at the lack of communication from Mozilla. Seems they would be more concerned with a obvious issue with one of their updates. Thanks Fred for the efforts to help.
FredMcD
  • Top 10 Contributor
4248 solutions 59425 answers

Was running Firefox in Safe Mode any help?

Start your Computer in safe mode with network support. Then start Firefox. Try Secure websites. Is the problem still there?

http://encyclopedia2.thefreedictionary.com/Linux+Safe+Mode Starting Any Computer In Safe Mode; Free Online Encyclopedia

Was running Firefox in Safe Mode any help? Start your '''Computer''' in safe mode with network support. Then start Firefox. Try '''Secure''' websites. Is the problem still there? http://encyclopedia2.thefreedictionary.com/Linux+Safe+Mode Starting Any Computer In Safe Mode; Free Online Encyclopedia

Chosen Solution

I did not need to utilize the Safe Mode suggestion.

Early on, I saw where changing the proxy settings "might" correct Firefox running slow. There were also some words of caution across the geek community in information I researched against altering how Firefox connects to the internet, (ie: proxy settings).

Today I had the time to dig deeper into this option and flipped back to "no proxy". Things have returned to normal, thank God. Sorry, not a big fan of the "Other Browsers".

My question at this juncture would be how, or why did the 63.0.1 Firefox update alter my connection settings? As I mentioned, I have been navigating around in cyberspace using Firefox as my primary browser, and never experienced an issue until now.

Thanks Fred McD for the suggestions. Just in case I have to revisit this problem in the future, I have logged some of your valuable links.

Hopefully I can consider this issue fixed and begin to browse on, again at 21st century speeds. Shoot, there were moments when I thought I heard the infamous dial tone it was so slow.

Thanks again.

I did not need to utilize the Safe Mode suggestion. Early on, I saw where changing the proxy settings "might" correct Firefox running slow. There were also some words of caution across the geek community in information I researched against altering how Firefox connects to the internet, (ie: proxy settings). Today I had the time to dig deeper into this option and flipped back to "no proxy". Things have returned to normal, thank God. Sorry, not a big fan of the "Other Browsers". My question at this juncture would be how, or why did the 63.0.1 Firefox update alter my connection settings? As I mentioned, I have been navigating around in cyberspace using Firefox as my primary browser, and never experienced an issue until now. Thanks Fred McD for the suggestions. Just in case I have to revisit this problem in the future, I have logged some of your valuable links. Hopefully I can consider this issue fixed and begin to browse on, again at 21st century speeds. Shoot, there were moments when I thought I heard the infamous dial tone it was so slow. Thanks again.
FredMcD
  • Top 10 Contributor
4248 solutions 59425 answers

That was very good work. Well done. Please flag your last post as Solved Problem so others will know.

That was very good work. Well done. Please flag your last post as '''Solved Problem''' so others will know.