[BUG] Forum takes about 20 minutes to load

Level1Techs Bug report
1

So, if I have a new browser session in firefox, opening this forum freezes with the 5 loading dots for about 10 minutes. It always works, but it takes ages.
After the page has loaded, it works normally for the rest of the session.

I have 3p scripts and 3p frames blocked, but javascript enabled in uBlock origin.
But even if I enable those and reload, it still just keeps “loading”.
I have never experienced this behavior on any other webpage…

If it’s some kind of anti-ai scraping or smthn, why not just use anubis?

2

sounds like a bug in ublock tbh

3

IIRC I even disabled it and tried, I’ll retry and let you know how it works with it disabled.
But even so, this is the only site it happens on, so more likely something ordinary on your side rather than UBo.

4

Works fine in Firefox and Brave on my end of things.

1 Like
5

Fine on Firefox, librewolf, and Chrome here

6

The same thing happens with uBO disabled.
This is something going on on your side.

Took even longer this time, about 20 minutes, and that was as I said with uBO disabled.

7

whats the error in the browser console?

1 Like
8

I don’t think there is an error, the page is loading, but very slowly it seems.
I can check if you tell me exactly how and what you want me to do before I start the session.

I tried in mullvad and brave (flatpak version) and those works just fine, so it’s a firefox vs this forum.
Also, the “normal” webpage (domain) also works just fine, it is only the forum (subdomain).

9

right click the page, go to inspect and there is usually a console tab

10 
Uncaught ReferenceError: chrome is not defined
    <anonymous> <anonymous code>:11
    <anonymous> <anonymous code>:29
    <anonymous> <anonymous code>:31
<anonymous code>:11:5
Uncaught ReferenceError: chrome is not defined
    <anonymous> <anonymous code>:692
    <anonymous> <anonymous code>:770
    <anonymous> <anonymous code>:772
<anonymous code>:692:18
ℹ️ Discourse v3.3.0.beta2-dev — https://github.com/discourse/discourse/commits/3e7601cada — Ember v5.5.0 app.js:240:11
[THEME 15 'Hamburger Theme Selector'] decorateWidget: Could not find widget 'menu-links' in registry
Element previously highlighted. To highlight again, first unset `dataset.highlighted`. 
<code class="hljs language-php-template" data-highlighted="yes">

If you want me to do it as it is loading, let me know.

11

Page loading fine for me…

Fennec on GrapheneOS

12

probably the before state while its loading then what appears after its done loading

the network tab might show what file its trying to load over a very long time, too.

13

I’ll check the network tab in a new session and let you know because there are no backlogs in that tab.
I’ll keep you posted.

14

I want to emphasize this is ONLY the forum (subdomain), everything else works normally.

Pretty much every js takes forever. (had to add txt suffix for forum)
forum.level1techs.com_Archive [25-12-02 17-57-04].har.txt (4.4 MB)

And here is a reload after it completed above, fast as lightning.
forum.level1techs.com_Archive [25-12-02 17-59-00].har.txt (4.4 MB)

Edit
There is a reference link in the console that for some reason did not get included in the copy/paste.

15

I’ve had this happen in firefox as well. If I don’t visit the site for a while from a certain work computer (Windows 10), it occurs again. Also with uBlock Origin, have tried it turned off.

16

off

2 Likes
17

If you’re the only one having a loading problem, this would indicate this is not a site-side issue…?

3 Likes
18

No, if it happened repeatedly AND on other webpages, maybe.
Also:

I provided logs and are ready to help out with debugging, but “it works here” or “maybe it’s you” is not helpful so please stop.
This is a bug report, please treat it as one.
Thank you.

19

Other people were saying that it works fine, I was just adding information that I’ve had this same problem occur as well. The opposite of “it works”. I don’t have logs to add because it’s currently not happening on my end. Not sure why so hostile.

2 Likes
20

We are. By adding more data for the folks that have to troubleshoot this.