Why com.apple.Webkit.GPU consuming a significant amount of CPU?

To me, this happen because I had another Mac user that had Safari open, I had to logout my current user and login to my user where I had Safari open, close everything and logout (not lock screen) from that user then come back to my regular user and the com.apple.Webkit.GPU process was gone. Hope this helps in this mystery.

FYI: The way how I find out this, was when I double click on the com.apple.Webkit.GPU process, I noticed that the "User:" shown was my other Mac user.

Yeah that's my daily workaround.

Few killall per day, keeps the doctor away.

killall com.apple.WebKit.GPU

Had the same issue. Killing the process in Activity monitor would only result in it coming back a few mins later. The only thing that got rid of the process was quitting Safari and only using Chrome.

oroooat wrote:

Hi there!

I just switched to an Apple Silicon Mac Mini M2 Pro from Macbook Pro Intel 2020 and noticed that the process "com.apple.webkit.GPU" is consuming a significant amount of CPU and memory, according to screenshots below.

Mac Mini M2 Pro - Ventura 13.2

Verify your software is up to date..

The current stable release of Ventura including bug fixes,  security updates  is macOS Ventura 13.2.1  

Keep your Mac up to date - Apple Support

Keep your Mac up to date - Apple Support

Verify your third party software is updated to date....

for browser issue, disable all extensions and/or plugins and compare your results.

It happens to me from time to time. The fans running fast for a long time. When I notice, I just kill the task in activity monitor and automatically ends the noise, but nothing wrong happens. The task starts again, but consuming much less resources. It seems like suddenly it bugs itself.

Then have a few suggestions ;

1 - Get Support Choose a product and we’ll find you the best solution.Start now and open an Apple Support Ticket as they are Apple Employees to deal will these types of issues . 

2 - Product Feedback - Apple and make it known to Apple regarding this ongoing issue 

If the perceived issue is reproducible on a consistent basis on Multiply different Apple Computer perhaps Apple Will deal with it.

From the image above, it appears your Google Chrome Helper might be the source of this issue

Google Chrome Helper (GPU) 884.9 MB Memory

Everybody wants a Soap Box the stand on.

Incase the Other Link, which may have been overlooked will be more fruitful.

2 - Product Feedback - Apple and make it known to Apple regarding this ongoing issue 

I don't believe that's the underlying issue. I've observed this behavior on a variety of macOS systems, (both with and without Google Chrome), and in each instance, it appears to be correlated with GPU processing tasks. This behavior can also be observed in Safari.

Running M1 Mac Mini with HDMI direct to Asus 27 " Display in Ventura 13.2 and Safari 16.3

Have 2 Active Tabs open in Safari

Refer to below image pertains specifically to " com.apple.webkit.GPU "

Arrive at you own conclusions

The quality of code at Apple (as well as other companies) has always been cyclical, with ups and downs. Currently, it seems we are in a down phase. Let's hope for better times. The memory leaks are really annoying.

Your link leads to the Apple Care Support Hotline/Chat.

How is an Apple Care support representative able to resolve a memory leak that the developer couldn't?

We are already on macOS 13.2 (13.3 around the corner) and the error was present in the b€ta.

It's certainly well-intentioned of you, but if someone from the core team doesn't address it, this error will persist like forever.

You aren't new here.

Do you really believe that?

Do you know how many bugs I have already reported that have simply been ignored for years?

The great feedback form doesn't even allow me to select the current macOS version.

That says enough about this program.

But let's not distract from the main task. The problem has existed for a while and Apple has not had the opportunity to fix it yet. We'll have to live with that. As long as it doesn't affect a important person, the bug will continue to persist across further versions, without anyone at Apple truly caring about it. Sad but true, but sad, but true...

TechArea wrote:

You aren't new here.

Do you really believe that?

Do you know how many bugs I have already reported that have simply been ignored for years?

The great feedback form doesn't even allow me to select the current macOS version.

That says enough about this program.

https://discussions.apple.com/content/attachment/d004e771-a211-4553-aa4b-0a560fdad8cf

But let's not distract from the main task. The problem has existed for a while and Apple has not had the opportunity to fix it yet. We'll have to live with that. As long as it doesn't affect a important person, the bug will continue to persist across further versions, without anyone at Apple truly caring about it. Sad but true, but sad, but true...

Proverb - "A little knowledge is a dangerous thing " .  A small amount of knowledge can mislead individuals into believing that they are more experienced and expert than what is actually the case."

There as been very little re-produceable evidence to support the above assertion

There has been sufficient advise offered for the User to make an informed and educated choice what the next course of action is required for this computer.

The suggestions have been put forth on a volunteer basis, in good faith and in the best interests of the computer which is the sole and only focus of this issue

Technically, the above User has Co-Oped the question from the " Author " and " Owner " of the Original Question

The user is welcome to join in and offer constructive information that will assist the Author of this question solve or workaround their Computer issue

Community etiquette guidelines - Apple Support