1692075 - Page wont render while tracker is not responding

Status: UNCONFIRMED

(Core :: Privacy: Anti-Tracking, defect, P3)

Description

[gregb212]

Attachment: 2021-02-10 17_06_37-.png

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:85.0) Gecko/20100101 Firefox/85.0

Steps to reproduce:

Load https://tmi.yokogawa.com/us/solutions/products/data-acquisition-equipment/high-speed-data-acquisition/dl950/ with:
Name Firefox
Version 85.0.2
Build ID 20210208133944
The page wont render, or renders a white page for 20 seconds while trackers time out. When the trackers time out, the page loads.

A friend reported the page loads fine with ublock origin installed, which I do not have. I have pfblockerng set up on a router. I did not see attempts to block the trackers in the pfblockerng log.

Actual results:

The page render is stuck for 20 seconds on a blank/white page. Screenshot of the network tab from debugtools is attached.

Expected results:

On chrome, vising the same page, the webpage renders within 3s.

Comment 1

[gregb212]

I tried loading the above link again today, and the page rendered in a time similar to my experience on chrome:

The trackers which took 20 seconds to respond now seemed to get blocked after <100ms because "a security error prevented the resource from being loaded"

I've no idea what changed... I did cycle the enhanced tracking options from standard to custom (disabled everything), then back to standard at some point. The laptop also went to sleep and woke up.

Comment 2

[gregb212]

Attachment: test from 2nd day. the page loaded normally

Comment 3

[Timea Cernea [:tbabos][inactive]]

Hi gregb212,
I am not able to reproduce this on macOS 10.15 on latest Firefox Release 85.0.2 Release version regardless if I choose to have standard tracking protection or Custom (blocked everything) so this might've been something intermittent.
Will leave this ticket open for 15 days, if you encounter this again and constantly please add a comment here so we can investigate further becuase at this point this is not actionable as it is.

Comment 4

[BugBot [:suhaib / :marco]]

The Bugbug bot thinks this bug should belong to the 'Core::Graphics: WebRender' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Comment 5

[gregb212]

Hello all,
Today I again reproduced the issue. After a few days of running with all enhanced tracking protection's disabled, I set it back to standard. I did not restart firefox. Then I attempted to load https://www.ford.com/suvs/mach-e/?bannerid=25050848|3093372|295846249|145504280|488307755 and it repeated the above described behavior. I have also captured a video of the behavior. It is shared from my onedrive as the filesize is too large to host here.

https://1drv.ms/u/s!AngvhX8BleHQgqIBLC6ycdlVVlRbJQ?e=G177XY

Comment 6

[Timea Cernea [:tbabos][inactive]]

Thanks for confirming this again! Still, I am not able to reproduce it but will move this issue over to a component so developers can help you investigate this further.

Also, when you reproduce this issue, can you please also disable your add-ons and refresh the page?

Comment 7

[gregb212]

Attachment: addons-disabled-feb-22-2021

Comment 8

[gregb212]

Attachment: render-delay-feb-22-2021

Comment 9

[gregb212]

Hi Timea,
I reproduced again today on https://itsfoss.com/esplot/
I went to about:profiles and restarted with addons disabled. The behavior persisted.
Enhanced tracking protection was set to "standard".

Comment 10

[gregb212]

I opened the same page on chrome, and it does not have the 20s delay.
I realized I had a company VPN on, so I turned it off, but it made no difference in firefox.

Comment 11

[gregb212]

I opened the itsfoss.com page on a separate computer. This was a surface book 2 running FF 85.0.2
The delay persists.

Comment 12

[gregb212]

On a whim, I decided to reboot my router. It is a PFSense router running pfblockerng. This is a software package that provides features identical to a pi-hole... that is ad and tracker blocking via DNS redirection. It will redirect identified ad and tracking servers to an empty local IP address... Upon rebooting, it seems that the behavior went away.

So it would seem that the rendering is delayed via certain tracking and ad server replies.

All that being said, I'm not sure why FF would not render the webpage when chrome does, with identical network configuration.
I still think there is a bug here.

Comment 13

[gregb212]

I should clarify, I disabled pfblockerng earlier, but did not reboot. I suspect that the block was still in a firewall cache or something.