WAIT: CPU usage - fan on all the time

Bugs
1

Browser: Chrome 115
OS: macOS

There’s lots of similar posts, but I’ve never experienced this before. Now I get it every time I open the Bricks builder - since 1.8.4

Activity monitor reports Chrome using 100% and more CPU and the fan is constantly on.
CPU: 3.6 GHz 8-Core Intel Core i9
GFX: Radeon Pro 580X 8 GB
RAM: 32 GB 2667 MHz DDR4

Really ought to be enough to handle things.

2

Hey @digismith - Perhaps the Bricks 1.8.4/8.5 update added a new background process or coincidentally Chrome pushed an update. I remember a year ago thinking there was an issue with a website I was building in Gutenberg but that same day had updated Chrome, turns out it was just Chrome related.

My previous 2014 iMac and 2018 Macbook (both intel based) would consistently have issues with any sites or browser based applications using heavy JS. Try toggling Chrome’s hardware acceleration setting or check Chrome’s changelog for any new experiment features. I had found in the past that new experimental features were added to Chrome and indeed causing issues with the fan. There’s a terminal setting you can apply to intel Mac’s that reduces or counteracts Chrome’s hardware acceleration issues (will try to find you that article).

Sidenote: Using an M1 Mac now and haven’t had any Chrome related performance issues. Apple’s silicon has truly been a game changer, if you plan on upgrading down the road

3

Hey @digismith,

thanks for your report.

What plugins are you using? Can you reproduce this issue with all plugins being disabled? If so please send some temporary credentials to help@bricksbuilder.io so we can investigate this. Please include a link to this forum thread.

Best,

André

4

Hi @aslotta - thanks for the response.
I am only able to reproduce on Localhost… so I will look at that. If I find anything useful I’ll let you know, but I’ll mark this as solved as I don’t think I’m going to track anything consistent down.

5

Hey @digismith ,

I’ve got the exact same issues.

Did you manage to resolve this?

Cheers, Jo

@aslotta FYI

6

Been working on non-web projects for a while. I have a Bricks build soon and will see, but I didn’t find a solution so much as it simply stopped happening.
I’m inclined to think it’s chrome - since it happens with a few other applications too (e.g. using 3D or virtual tours).