PowerToys icon indicating copy to clipboard operation
PowerToys copied to clipboard

PowerToys Run Memory Leak

Open OVERKILL27 opened this issue 1 year ago • 5 comments

Microsoft PowerToys version

v0.74.1

Installation method

PowerToys auto-update

Running as admin

Yes

Area(s) with issue?

PowerToys Run

Steps to reproduce

After searching for "recycle bin" using PowerToys Run, the PowerToys.Run process rapidly started increasing its memory consumption. After approximately a minute it started using over 40 GB and went to over 50 GB after about 10 minutes image PowerToysReport_2023-10-07-21-58-13.zip

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Other Software

No response

OVERKILL27 avatar Oct 07 '23 11:10 OVERKILL27

I cannot reproduce this. Does this heppen every time you type in recycle bin?

/needinfo

Aaron-Junker avatar Oct 07 '23 12:10 Aaron-Junker

I just tried it a couple of times again and yes, it happened those times as well.

OVERKILL27 avatar Oct 07 '23 12:10 OVERKILL27

I am also experiencing this issue. I just use PowerToys Run normally by pressing Win+R and search or execute applications, and the PowerToys.Run process just consumes all of my system memory. (Sorry that I am not able to give specific reproduction steps, as I just use the functionality in a very standard way). Below is a screenshot:

圖片

I am currently on PowerToys v0.77.0.

This issue didn't used to exist before in v0.6x.x, I only upgraded from v0.6x straight to v0.77 like 2 days ago, and am already encountering this issue.

pcmaniac23 avatar Jan 17 '24 08:01 pcmaniac23

I also confirm this issue. Consumes all available RAM and leads to system freeze!

macsunmood avatar Jan 20 '24 01:01 macsunmood

Same here, it was taking almost all of my memory I didn't even use it today My Powertoys version: 0.78.0

image

Fus3n avatar Feb 07 '24 19:02 Fus3n

/dup https://github.com/microsoft/PowerToys/issues/27387

ethanfangg avatar Mar 08 '24 20:03 ethanfangg

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!