Bug: beardie-nm-connector process using lots of power

[bentoon00]

[ Similar to #26 ]
After checking activity monitor, the beardie-nm-connector process is using far more power in the background than any other open and active process, even Spotify when actively playing music. The process doesn't appear in the battery menu tab as high usage, only Google Chrome. Perhaps this has something to do with the installed Chrome + Beardie extension?
The process's CPU and power usage stays the same when Spotify is playing, paused and closed (completely).

Process sample attatched below
Device: M1 Max MacBook Pro 16" - Battery health 99%
OS: Ventura 13.2.1

Sample of beardie-nm-connector.txt

[bentoon00]

Process is making ~2 million unix sys calls a second

[sebastienbarre]

Can see that too on my Macbook Pro M1 Max :( Had to kill the process before it sets my knees on fire.

[vityevato]

@sebastienbarre #26

[sebastienbarre]

@Stillness-2 Thanks, but it just doesn't build for me. I opened the project in XCode, hit "Build", and it is failing in many different ways..

[vityevato]

@sebastienbarre Make a copy from .devconfig.xcconfig.template to .devconfig.xcconfig in the root of the repository, and replace the inside with the correct one

[sebastienbarre]

Thx. Though now it's only "No certificate matching 'Sign Identifier' found: Select a different signing certificate for CODE_SIGN_IDENTITY, a team that matches your selected certificate, or switch to automatic provisioning."

Can this project be built locally without a certificate?

[vityevato]

I've never tried it :)

[vityevato]

Everything is configured to sign for further distribution not through MAS

[sebastienbarre]

I'm afraid I don't know what that means.