Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

High CPU usage/memory leak in Joplin 2.13.5 #18

Closed
runrunrirun opened this issue Feb 6, 2024 · 3 comments
Closed

High CPU usage/memory leak in Joplin 2.13.5 #18

runrunrirun opened this issue Feb 6, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@runrunrirun
Copy link

For some reason the plugin seems to continuously use CPU and increase memory usage when installed on 2.13 or 2.14 at least on macOS Sonoma 14.3 Intel. This is the only installed plugin. I have ~500 notes in Joplin.

@rsandz rsandz added the bug Something isn't working label Feb 18, 2024
@rsandz
Copy link
Owner

rsandz commented Feb 18, 2024

Thank you for the report @runrunrirun!

Do you have additional info on the following?

  • Is the high CPU + memory happen transiently? Does it happen only on a specific action or does it persist?
  • Is high CPU + memory usage evident when Joplin is started? Or does it take some time for the performance to degrade?
  • Would you be willing to share your Joplin vault privately to help with troubleshooting this issue?

rsandz added a commit that referenced this issue Feb 19, 2024
rsandz added a commit that referenced this issue Feb 19, 2024
rsandz added a commit that referenced this issue Feb 19, 2024
@rsandz
Copy link
Owner

rsandz commented Feb 19, 2024

There was an infinite loop that can occur when there are a lot of notes for a single day. (Caused by pagination logic that didn't actually increment the page). #19 may fix the performance issues seen here.

@runrunrirun
Copy link
Author

Missed the earlier post, sorry! But it appears to be fixed now, tested in Joplin 2.14.16, memory and CPU use are now stable with this plugin active, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants