setTimeout in uhsript.js eating up CPU

[CrutyRammers]

Also here https://www.pistonheads.com/gassing/topic.asp?h=0&...

[thebraketester]

40% CPU load on MBP 2017.... ridiculous

[Jack Mansfield]

Hi piston25m - as discussed, I've logged this onto our system for it to be looked at

Cheers

Jack

[bitchstewie]

50% CPU usage in Chrome task manager just looking at a tab.

And that's with a uBlock god knows what it would be like with ads

[johnwilliams77]

piston25m said:

You can use this extension in the meantime to "fix" the problem: https://addons.mozilla.org/en-US/firefox/addon/dis...

Any chrome extensions?

[bitchstewie]

Still 55% CPU usage in Chrome from a single PH tab.

It's not good

[scjgreen]

Only 5% CPU Usage here

Windows 10
Chrome

[bitchstewie]

scjgreen said:

Only 5% CPU Usage here

Windows 10
Chrome

Could I check if you're looking in Windows Task Manager or in Chrome's inbuilt task manager?

[768]

I can't believe this still isn't fixed.

There must be so many known security vulnerabilities racking up with the amount of care the codebase is getting.

[anonymous-user]

768 said:

I can't believe this still isn't fixed. There must be so many known security vulnerabilities racking up with the amount of care the codebase is getting.

Agreed. PH seems to be allowing all manner of attacks at users of the site and they must know what's going on. This needs a serious sorting out or they're going to find themselves facing significant liability issues. It's poor site management and just not good enough.

[skwdenyer]

There are an *insane* number of resource calls on the forums now. A lot is to do with some poorly-thought-through analytics - the same code being called multiple times, say. I note they've implemented Hotjar now, too, so assume you're being screen-recorded whilst you use the site?

It has got so bad that my brand new MacBook Pro takes multiple seconds to load a forum page. So, sadly, I've had to disable all Javascript on the site - and as if by magic performance is now back up to speed.

If anyone at PH towers would like some help with this stuff, my wife does it for a living...

[RacingPete]

We have fixed (hopefully) the infinite loop - let us know if you see improvements.

[johnwilliams77]

RacingPete said:

We have fixed (hopefully) the infinite loop - let us know if you see improvements.

That's a lot quicker than the fonesafe scam!

[768]

I'm not seeing it fixed yet.

FWIW, it's the first setTimeout in here at the start of the document ready function. Although it looks as though there's another potential offender further down.

[tirolo_]

768 said:

I'm not seeing it fixed yet.

FWIW, it's the first setTimeout in here at the start of the document ready function. Although it looks as though there's another potential offender further down.

latest version is 5676 you can see it here for some reason you are still getting the old version (which is another bug already in the backlog) maybe try cleaning your cache? .. gonna look into it tomorrow to make sure everyone gets the latest...

[768]

Good to know. I used a private browsing window to avoid any client side cache.

[768]

I'm getting served the updated version now. Much better, thank you.

[RacingPete]

768 said:

I'm getting served the updated version now. Much better, thank you.

And now we have rolled back - needs a little bit of work to untangle this - sorry, but working on it.