🐞 High CPU load on lsd and pkd processes when CodeEdit is open

[TomDev234]

Description

High CPU load of lsd and pkd when running CodeEdit.

To Reproduce

Install published version of CodeEdit

• Start Codedit
• Open Activity Monitor
• Search for "lsd" or "pkd" and see high usage

Expected Behavior

Normal CPU load

Version Information

CodeEdit: 0.0.3
macOS: 13.2.1
Xcode: 14.3

[matthijseikelenboom]

Can you elaborate a bit more? This is too little information to do something with.

Maybe screenshots from Activity Monitor or profiler data from Xcode?

[TomDev234]

lsd and pkg are responsible for loading plugins. Can there be a problem with CodeEdit?

[matthijseikelenboom]

Sure, but I'm not seeing "proof" of your claim? Where do you get your claims from.

Also, you haven't set an issue title.

[austincondiff]

Please be more specific. Closing this issue because it is pretty vague.

[BienGudBoy]

@austincondiff I can confirm this issue also happens on my machine. Right when I open the app, lsd and pkd eats up around 40 - 50%, sometime even spikes to over 100%. Both of these goes away when I exit.

Our weather is quite hot right now in the summer, and because I'm using a Macbook Air M1 (16/256), this causes my laptop to get quite hot, even when doing nothing until I close it.

[TomDev234]

I am using Sublime Text now.

[tiernan]

Not sure why this is closed. I noticed high pkd and led usage on my computer and was searching for an answer. I came across this, and realised I had CodeEdit installed. This is definitely still an issue and I have uninstalled the software. You should open this ticket back up.

Proof?

Open CodeEdit, have two open documents with some text in them. Now go and open activity monitor: pkd and lsd processes sit around 30% (on M1 Max). Close CodeEdit, pkd and lsd go to 0. There you go...

No idea why your software causes issues with PluginKit but it does.

[matthijseikelenboom]

Just noticing the comments, thanks for posting. I'll open it back up.

Note that we're in active development and that this is NOT a finished product.

That said, it seems that this issue is not occurring when ran directly from Xcode. (At least "not on my machine")

(The reason this was closed is because there was not much info posted before)