Delay/freeze on GitHub and some forums

[back2themoon]

It's a while I'm noticing about a 2-3sec. delay when opening GitHub links, during which the browser essentially freezes. Example: open an unrelated website, and open/refresh any GitHub link on another tab, while scrolling the previous website up/down. The scrolling pauses and nothing can be done in Pale Moon during these few seconds, until the Github page loads. The pause can be noticed even without scrolling on another website.

Exact same problem on the Emsisoft Forums, after a recent forum update they did (was fine previously). Also tried Safe Mode/clean profile. Is this some sort of compatibility issue?

[New Tobin Paradigm]

No problems here on Release and Unstable 20170312 or 20170314.

[trava90]

I had this happen to me on unstable yesterday, but GitHub was the only tab open at the time and I've not been able to reproduce it since.

[back2themoon]

Thanks for testing. Can reproduce it every time, I think it's going on for a few months. Uninstalled A/V. Also happens on Windows Safe Mode, but the delay is shorter and less noticeable. On Github, even by clicking on a single link, I usually get this Error in the Console:

Code: Select all

Content Security Policy: The page's settings blocked the loading of a resource at about:blank ("base-uri https://github.com")

...and a bunch of warnings (attached).

[New Tobin Paradigm]

Yes.. That does happen but it doesn't actually break anything in this specific case. So not that.

[back2themoon]

Just noticed that the issue is much more noticeable on x86 Pale Moon. The 64-bit version 'recovers' almost immediately.

[Moonchild]

I use x86 all the time in my daily browsing, including GitHub, and I do not notice any delays or freezes, myself.
You should realize though that script-heavy websites will take considerable processing time while loading because JavaScript is being compiled into machine code on-the-fly. When using timing-critical features like smooth scrolling, you will notice this. It's an inevitable result of JIT-compiled scripting. Still, this would normally not cause seconds of unresponsiveness.

[Fedor2]

I use x86 too, difference between enabled and disabled js on github and emsisoft are the same, less than a second

[back2themoon]

I probably expressed this wrongly. The mouse-scrolling is irrelevant, just a method to easily present this issue. At least on my old CPU (Intel Q9650), I'm noticing significant x86/x64 performance difference.

So I guess the question would be, if this is something to be expected with specific websites (however only on GitHub there's this big difference). Moonchild's response suggests it is possible (although the 1-2 sec. freeze always occurs on x86). Perhaps GitHub triggers something that the x64 version handles significantly better or that causes the x86 to 'block' momentarily?