iplan 1.9.0 uses CPU resources excessively

[SokolovskyMaxim]

Запись экрана от 2023-07-15 13-23-08.webm

as can be seen from the screencast, excessive consumption of processor resources occurs during the operation of the application and stops when it is completed

It looks like a memory leak or something like that

[SokolovskyMaxim]

there are no logs when running through the terminal

[iman-salmani]

Thank you for reporting this I tested the previous version and clearly something is wrong.

If you wanna downgrade to the previous version:

flatpak update --commit=99bd4408cdbd65c95d18029e050802f4e769a5572d5b78f3eaaa6692d2fba53f ir.imansalmani.IPlan

Do you notice huge CPU usage change while doing specific task inside the app?

there are no lags

Do you mean logs?

[SokolovskyMaxim]

Yes, the previous version does not have such a bug.

And yes, I meant logs

[niktss]

This happens to me as well, on 1.9.2/Fedora 38

Can also confirm that when launched from the terminal the issue does not occur

[SokolovskyMaxim]

At the first launch after the corrective update, I also had manifestations of the old error. But then, after restarting the application, the problem disappears and the error is not reproduced

[iman-salmani]

Hi @HeadPlug Do you have this problem even after navigating to the calendar page and back to a project page?

[niktss]

At the first launch after the corrective update, I also had manifestations of the old error. But then, after restarting the application, the problem disappears and the error is not reproduced

I've restarted both the application and my computer multiple times; it keeps happening.

Hi @HeadPlug Do you have this problem even after navigating to the calendar page and back to a project page?

No. After visiting Calendar, the issue solves itself. If I close IPlan and open it again, the issue will reoccur, and then I have to go to Calendar again. This happens even if I kill the iplan process. If I open IPlan from the terminal though, the issue doesn't happen.

Kooha-2023-07-20-04-24-43.webm

[SokolovskyMaxim]

I've restarted both the application and my computer multiple times; it keeps happening.

You're right, the error occurs when running through the application menu or through the search. I have a launch assigned to a keyboard shortcut, this is equivalent to launching from the terminal, so I did not notice that the error continues to be reproduced in extreme cases

[niktss]

I've cracked it, I think - it's the .desktop file.

I edited it down to this, and the issue does not happen anymore: I was however in a rush, so I don't remember what I deleted, but it should be fairly trivial to troubleshoot now.

[niktss]

Issue is resolved when changing Nameto Name[en]=IPlan instead of Name=IPlan --command=iplan is the culprit. Changing it to --command=ir.imansalmani.IPlan solves the issue, removing it altogether also works. I'm not sure if this breaks anything I thought I'd resolved it, but it was just that I'd managed to make it run in a more "Flatpaked" manner, which must have hid it from my task manager which is also a Flatpak 🤦‍♂️

[muelsyse-az]

Just want to give an update on this issue. I was using the app and realized that my battery usage went up significantly and my fans started ramping. Confused, I went to look at my System Monitoring Center and found out that iPlan was using ~20% CPU when run. I am on iPlan 1.9.2 running Fedora Silverblue 38.

Since I have a rather small battery (40Wh), this makes it unfeasible for me to use the app when on battery (which I often do for prolonged durations due to school). I hope this is fixed, but I understand that this may take a while.

[niktss]

Just want to give an update on this issue. I was using the app and realized that my battery usage went up significantly and my fans started ramping. Confused, I went to look at my System Monitoring Center and found out that iPlan was using ~20% CPU when run. I am on iPlan 1.9.2 running Fedora Silverblue 38.

Until this is fixed, you can use the workaround discussed above - simply go to the Calendar tab after every app launch, and CPU usage should normalise itself.

[muelsyse-az]

@niktss Thanks! I'll give that a go.