Fenix: Delay when opening the first page after opening Firefox for Android (ublock?)

Created on 10 Nov 2020  ·  4Comments  ·  Source: mozilla-mobile/fenix

Steps to reproduce

Close the browser and reopen it. Visit a website.

Expected behavior

Display the website immediately without any delay.

Actual behavior

Display that the website has an Insecure Connection and Firefox waits for 8-10 seconds with a white background and then displays the page.
This only happens for the first page visited after opening Firefox. All pages open normally after the first page delay.
Add-ons : HTTPS Everywhere and uBlock Origin.

firefox

Device information

Xiaomi Mi A1 (LineageOS) and Xiaomi Mi A3(Stock)

  • Android device: 10
  • Fenix version: 82.1.3
performance triage

Most helpful comment

Hi @mcomella .
I tried to reproduce the problem in different scenarios:
1). Only with uBlock: 7-8 seconds delay.
2). Only with HTTPS Everywhere: 10 seconds delay.
3). With both uBlock and HTTPS Everywhere: 8-10 seconds delay.
4). Without using any extensions: 1-2 seconds delay or no delay.

I think the problem is not specific to uBlock.
I also tried out the new TOR browser based on fenix. It too has the same problem(Extensions: HTTPS Everywhere and NoScript)
tor

All 4 comments

@Mohan40 Are you able to reproduce the delay without ublock? If so, we're aware of an issue with slow first page loads with ublock https://github.com/mozilla-mobile/fenix/issues/8251 but we're unable to do any more about – it would be ideal if you could report this to the ublock developers.

We felt the insecure connection was an unrelated issue so I filed a separate ticket for that: https://github.com/mozilla-mobile/fenix/issues/16558 Let's only discuss the delay in this bug.

Hi @mcomella .
I tried to reproduce the problem in different scenarios:
1). Only with uBlock: 7-8 seconds delay.
2). Only with HTTPS Everywhere: 10 seconds delay.
3). With both uBlock and HTTPS Everywhere: 8-10 seconds delay.
4). Without using any extensions: 1-2 seconds delay or no delay.

I think the problem is not specific to uBlock.
I also tried out the new TOR browser based on fenix. It too has the same problem(Extensions: HTTPS Everywhere and NoScript)
tor

Triage: we were able to reproduce with HTTPSEverywhere and ublock but not other add-ons. We still believe it's likely to be the code run by the add-ons (i.e. there's nothing we can do). One thing we can check is if we can reproduce the same delay in fennec. If so, then it's more evidence that it's due to code run by the add-ons and the issue should be filed against the specific add-ons. If not, we should file an issue against GeckoView because this is a regression.

Was this page helpful?
0 / 5 - 0 ratings