Google Chrome leaves processes around each time is closed

[nimrod]

Hi,

recently Google Chrome started to leave around a "chrome --enable-crashpad" process every time I closed it. Each of such processes sucks 25% of CPU. If I open another instance of Chrome and I close it, another process is created and reaches the 25% of CPU, and so on and so forth. Obviously the fans roar a lot until I don't kill every such processes.

The first time I open Chrome one of these processes is started, but it runs smoothly even around 0% of the CPU. Fans are quite silent.

I have three PC all equipped with Bullseye and regularly updated, but only one shows this behaviour. It's a Sony Vaio laptop, very good for me except for this strange problem.

Thanks in advance.

[Jeremy Ardley]

On 17/5/22 6:23 am, nimrod wrote:
> Hi,
>
> recently Google Chrome started to leave around a "chrome
> --enable-crashpad" process every time I closed it. Each of such
> processes sucks 25% of CPU. If I open another instance of Chrome and I
> close it, another process is created and reaches the 25% of CPU, and
> so on and so forth. Obviously the fans roar a lot until I don't kill
> every such processes.
>
>

I too have recent problems with Chrome. Playing videos such as on
youtube often result in the cursor flickering and the whole browser
becomes unusable. Sometimes I have just enough input that it will
recognise me hitting the 'x' and will then pop up a message about the
browser being unresponsive. Other times I have to use a kill -9

I upgraded to the latest Version 101.0.4951.64 (Official Build) (64-bit)
but the problem still happens.

--
Jeremy