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

Fóram Tacaíochta

Cuireadh an snáithe seo sa chartlann. Cuir ceist nua má tá cabhair uait.

is it possible to not have a delay at startup while forcing e10s?

Postáilte

Hi, with FF 48, I have create then set the pref browser.tabs.remote.force-enable to true so it enables e10s despite my add-ons. It works well but there is a delay at startup :(

Can I improve the startup time when this preference is set to True? Thanks :)

Hi, with FF 48, I have create then set the pref browser.tabs.remote.force-enable to true so it enables e10s despite my add-ons. It works well but there is a delay at startup :( Can I improve the startup time when this preference is set to True? Thanks :)

Tuilleadh mionsonraí faoin chóras

Breiseáin Shuiteáilte

  • Shockwave Flash 22.0 r0

Feidhmchlár

  • Firefox 48.0
  • User Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:48.0) Gecko/20100101 Firefox/48.0
  • URL Tacaíochta: https://support.mozilla.org/1/firefox/48.0/WINNT/fr/

Eisínteachtaí

  • FireFTP 2.0.28 ({a7c6cf7f-112c-4500-a7ea-39801a327e5f})
  • gtranslate 0.13.1 ({aff87fa2-a58e-4edd-b852-0a20203c1e17})
  • Multi-process staged rollout 1.0 (e10srollout@mozilla.org)
  • uBlock Origin 1.8.0 (uBlock0@raymondhill.net)
  • Firefox Hello 1.4.3 (loop@mozilla.org) (Neamhghníomhach)
  • Map This 0.3.1.1-signed.1-signed.1-signed ({05f6a7ea-896b-11da-8bde-f66bad1e3f3a}) (Neamhghníomhach)
  • Pocket 1.0.4 (firefox@getpocket.com) (Neamhghníomhach)

JavaScript

  • incrementalGCEnabled: True

Grafaic

  • adapterDescription: IGFX
  • adapterDescription2: AMD Radeon HD 8600M Series
  • adapterDeviceID: 0x0416
  • adapterDeviceID2: 0x6660
  • adapterDrivers: igdumdim64 igd10iumd64 igd10iumd64 igdumdim32 igd10iumd32 igd10iumd32
  • adapterDrivers2: aticfx64 aticfx64 aticfx64 aticfx32 aticfx32 aticfx32 atiumd64 atidxx64 atidxx64 atiumdag atidxx32 atidxx32 atiumdva atiumd6a atitmm64
  • adapterRAM: Unknown
  • adapterRAM2: 1024
  • adapterSubsysID: 1978103c
  • adapterSubsysID2: 0000000c
  • adapterVendorID: 0x8086
  • adapterVendorID2: 0x1002
  • direct2DEnabled: True
  • directWriteEnabled: True
  • directWriteVersion: 6.3.9600.18123
  • driverDate: 3-23-2016
  • driverDate2: 8-3-2015
  • driverVersion: 10.18.14.4414
  • driverVersion2: 15.200.1062.1004
  • info: {u'AzureCanvasAccelerated': 0, u'AzureCanvasBackend': u'direct2d 1.1', u'AzureFallbackCanvasBackend': u'cairo', u'AzureContentBackend': u'direct2d 1.1', u'ApzWheelInput': 1}
  • isGPU2Active: False
  • numAcceleratedWindows: 1
  • numTotalWindows: 1
  • supportsHardwareH264: Yes; Using D3D11 API
  • webglRenderer: Google Inc. -- ANGLE (Intel(R) HD Graphics 4600 Direct3D11 vs_5_0 ps_5_0)
  • windowLayerManagerRemote: True
  • windowLayerManagerType: Direct3D 11

Sainroghanna Athraithe

Éagsúil

  • User JS: No
  • Inrochtaineacht: Níl

Úinéir na ceiste

up?...

up?...
guigs 1072 réiteach 11697 freagra

It was disabled for "A11y clients, RTL interfaces, and touchscreens will not be selected in the first round, nor will users running Windows XP" for lack of compatibility.

Try disabling the addon " Multi-process staged rollout 1.0 (e10srollout@mozilla.org) " with the configuration set to try.

It was disabled for "A11y clients, RTL interfaces, and touchscreens will not be selected in the first round, nor will users running Windows XP" for lack of compatibility. Try disabling the addon " Multi-process staged rollout 1.0 (e10srollout@mozilla.org) " with the configuration set to try.

Úinéir na ceiste

I disabled the addon "Multi-process 1.0" but it has no effect on FF startup..

I disabled the addon "Multi-process 1.0" but it has no effect on FF startup..
John99 971 réiteach 13138 freagra

I have noticed a few similar comments on the support forum. No idea yet whether we are just seeing a few edge cases or whether this may be a bigger problem than expected.

If you turn on telemetry at least developers are made aware of the issue. If you use FHR you get your own data on startup (after a couple of weeks) rather than needing to rely on a subjective impression.

I have noticed a few similar comments on the support forum. No idea yet whether we are just seeing a few edge cases or whether this may be a bigger problem than expected. If you turn on telemetry at least developers are made aware of the issue. If you use FHR you get your own data on startup (after a couple of weeks) rather than needing to rely on a subjective impression. * [[Firefox Health Report - understand your browser performance]] * [[Share telemetry data with Mozilla to help improve Firefox]]