1659739 - Page content is not completely loaded https://www.crazygames.com

Status: RESOLVED WORKSFORME

(Web Compatibility :: Site Reports, defect)

Description

[Alin Ilea, Desktop QA]

Attachment: 2020-08-18_17h54_31.mp4

Affected versions:

Release 79.0, 80 RC, Nightly 81.0a1 (2020-08-18).

Tested on:

Windows 10, Windows 7

Preconditions:

Go to about:config and set: layers.acceleration.disabled to TRUE.

Steps:

1. Launch Firefox with a new profile, the pref from preconditions to true and go to: https://www.crazygames.com/t/webgl

Actual result:

The page content is not fully loaded.

Expected result:

All the page content should be loaded accordingly.

Note: If the issue is not reproducible on first attempt, try 2-3 times with new profile and layers.acceleration.disabled to TRUE, refresh the page..The issue seems to be intermittent.

Regression range:

I will try to find if this is a regression but given the fact that the issue seems to be intermittent could be hard to find a regression range.

Comment 1

[Nicolas Silva [:nical]]

I can reproduce this behavior with WebRender as well. I'd be surprised if the issue is related to the rendering backend, because there is no image in the DOM at all (according to devtools) in the cells where nothing shows up, whereas there is one in each cell that is displayed correctly.

There's also a bunch of CORS and resource loading error showing in the console.

A regression range would be very helpful.

Comment 2

[Darkspirit]

Gnome Xwayland, Debian Testing
Nightly and 68 with Basic: As in comment 0, only 25 images are shown by default or after one F5. It's intermittent. With 61 it could occur in rare cases.
Chromium 83: 25 images are shown instantly, then the rest.

Comment 3

[Nicolas Silva [:nical]]

I'm going to bounce this back to core::general because the graphics backend doesn't affect this issue. I suspect that it's some kind of resource loading issue closer to network than graphics.

Comment 4

[Tania Maity (:tmaity)]

Alin, what's your Severity suggestion for this bug?

Comment 5

[Alin Ilea, Desktop QA]

I would suggest S3 severity since the issue is intermittent, it is not reproducible all the time and in some cases it works after page refresh. Thank you.

Comment 6

[Alin Ilea, Desktop QA]

I will move this to Core: Networking. If this is not the correct component please feel free to change it to an appropriate one.
Thanks.

Comment 7

[Cristian Fogel [:cfogel]]

Just encountered the same issue while checking the site.
Confirming that the issue reproduces for 81.0b2 as well.

Ran some checks and:

• Ubuntu 20 - 81.0b2 (not loading);
• macOS 11.0 - 81.0b2(was loading) but 80.0(not loading);
• Windows 10 - 81.0b2(was loading).

In my case, all the settings were default; and as confirmed with Alin, that the issue reproduces more with the preff-flip but it's not the main trigger.

Comment 8

[Kershaw Chang [:kershaw]]

(In reply to Alin Ilea from comment #6)

I will move this to Core: Networking. If this is not the correct component please feel free to change it to an appropriate one.
Thanks.

I can locally reproduce this issue, but I see no networking related errors. All requests are completed without a problem.
From the http log, I saw the http request for the last image https://images.crazygames.com/games/free-rally-2/cover-1592474501010.png?auto=format,compress&q=75&cs=strip&ch=DPR&w=178&h=100&fit=crop was not even created.
I think this issue might be more related to DOM, so I'd like to change the component and see if someone has an idea about this.

Comment 9

[Mirko Brodesser (:mbrodesser-Igalia)]

Hiro: IIRC, you've worked on image loading code, do you have an idea, what the correct component should be?

Comment 10

[Hiroyuki Ikezoe (:hiro)]

I haven't looked at all, but if it's caused by bug 1076583 (I am suspecting it's very likely), "DOM: Core&HTML" seems reasonable to me. Even if it isn't, the root cause was something related to DOM attributes, "DOM: Core&HTML" is the reasonable component I believe.

Comment 11

[Hiroyuki Ikezoe (:hiro)]

I will look into detail tomorrow.

Comment 12

[Hiroyuki Ikezoe (:hiro)]

This is not related to lazy loading images. Those elements which don't have images don't have <img> element either. So I suppose the site does something by script (I guess by IntersectionObserver).

Comment 13

[Hiroyuki Ikezoe (:hiro)]

I think I finally found one of the triggers of this issue is. I think it's dom.timeout.defer_during_load. With dom.timeout.defer_during_load=false, the issue happens less frequent.

Anyways, this is a very timing specific issue when script runs or some such.

Comment 14

[Hiroyuki Ikezoe (:hiro)]

I did mozregression.
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=bb2895bfd1bc3d83c309e904dbe74e0c60c3fac9&tochange=06e3993985b77e62c9b6ee1f9dba87da407eb6d1

Indeed bug 1270059 made significantly worse this issue. That said, I think the site assumes a not-good thing that is that setTimeout (with 0) callbacks are invoked soon (before page loading finished?).

Comment 15

[Ksenia Berezina [:ksenia]]

We've looked at the site during triage and the issue is not reproducible anymore.