openmtp icon indicating copy to clipboard operation
openmtp copied to clipboard

Please update the Electron to prevent system-wide lag on macOS 26

Open tkafka opened this issue 5 months ago • 9 comments

See https://mjtsai.com/blog/2025/09/30/electron-apps-causing-system-wide-lag-on-tahoe/ and https://github.com/electron/electron/issues/48311#issuecomment-3332181420 - Electron was causing huge constant CPU usage on macs, and they merged in the fix.

tkafka avatar Oct 01 '25 12:10 tkafka

I am not sure if the version of Electron.js used in OpenMTP is affected by this. I use OpenMTP daily on my Mac Tahoe and have never seen any spike in usage.

Will update the electronjs if I hear complaints.

I am working full time on a major UI rework that will remove Electron.js from OpenMTP.

ganeshrvel avatar Oct 01 '25 12:10 ganeshrvel

Thank you for a swift reply!

I made a script to list all the affected mac apps, and thought I'd write an issue for the ones I use often :), but as OpenMPT is not an app that I'd need to run 24/7, I guess not updating is fine. Will be looking forward to the new electron-free version!

Thanks for OpenMTP! Tomas

tkafka avatar Oct 01 '25 13:10 tkafka

Thanks for the note. Will create a patch if I hear more complaints. You are awesome!

ganeshrvel avatar Oct 01 '25 13:10 ganeshrvel

Thanks for the great tool! It's what I use for loading maps into my garmin :).

tkafka avatar Oct 01 '25 16:10 tkafka

Awesome. I just got myself a few devices for building the next gen OpenMTP, a Garmin watch was one of them. Garmin devices are one of my top priorities. 👍

ganeshrvel avatar Oct 01 '25 16:10 ganeshrvel

https://github.com/avarayr/shamelectron is a great site tracking apps that have yet to fix the Mac lag bug. OpenMTP is on the list so might be worth updating the electron version

BB-BenBridges avatar Oct 24 '25 14:10 BB-BenBridges

Unfortunately, high GPU usage can be observed due to the Electron app bug. However, since people don’t use OpenMTP for long periods, it’s not too disturbing. In the future, it would definitely be worth updating, though it is not as bothersome as with other applications.

polinomad avatar Nov 06 '25 20:11 polinomad

Interesting. The thing is the Electron version used in OpenMTP right now is quite old. I will need to update it to the latest Electron version to fix this, and there is no telling what kind of breaking changes will come with that. There have also been issues with the Node native modules related to an npm version, so it is all just hanging in there.

I am mainly focusing on the next gen OpenMTP which will come with a more "nativeish" ui. So unless this issue becomes too apparent, I will keep concentrating on releasing the new version of OpenMTP.

ganeshrvel avatar Nov 06 '25 20:11 ganeshrvel

Thank you for the information.
Actually, if you are planning to release a new generation of OpenMTP anyway, I think it is really unnecessary to deal with the current version, at least because of the Electron update.
As I wrote before, it is not that disturbing, since when the program is just running it does not cause any load, only when you actually do something in it.
Thank you for your work on behalf of the community as well.

polinomad avatar Nov 07 '25 07:11 polinomad