-
-
Notifications
You must be signed in to change notification settings - Fork 13
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 memory Usage #53
Comments
In the Interm, I have added 64GB of page-file on an SSD to mitigate to continue operation. I also have stopped adding songs until the current queue is exhausted. (I believe i have 5-6k still being added) Obviously not optimal but will allow the app to run for now. It would be a major PIA to requeue everything. I could imagine that this will degrade the app once it starts being utilized. |
Does the amount stay high until the app is closed or does clearing items in the download queue fix the issue.
…On Sunday, November 10th, 2024 at 9:30 AM, solunafantasy ***@***.***> wrote:
In the Interm, I have added 64GB of page-file on an SSD to mitigate to continue operation. Obviously not optimal but will allow the app to run for now. I could imagine that this will degrade the app once it starts being utilized.
—
Reply to this email directly, [view it on GitHub](#53 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/BESVWLMMWE6DKIVBJI3INHDZ74RUPAVCNFSM6AAAAABRQAYRXGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRWGY2TQNRRG4).
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
It drops from 20GB to 13GB of ram after I clear completed downloads. Apologies it took so long to respond, i was afk all day. Surprisingly, it never crashed. Keep in mind only a third of the queue completed and its continuing to download. |
The latest commit substantially reduced the memory usage on my end, ~2.3GB for 625 songs down to ~270mb (290mb with download queue thumbnails). Clearing download queue still doesn't clear memory used by the deleted widgets, so I'll hold off on closing this issue until I can find an acceptable solution. The bulk of the usage was in the icons on various buttons, I didn't think much of it because the png files themselves are only a couple hundred bytes large but I suppose pyqt does something to them in the background with QIcon which causes them to use additional memory. The app now reuses icons, instead of making 625 spotify icons for 625 songs it makes 1. *Just a note for any users who are attempting to use onthespot on a low spec pc, the cli interface sits at ~90mb regardless of the number of songs queued. |
Feature Description
I am seeing extreme memory usage, more notable when adding 2.5K songs in queue. I first noticed this when Spotify and browsers crashed due to being out of memory, ( I don't normally use a page-file, I have 32GB of RAM)
Justification
Better memory management will avoid systemwide issues/improve performance. This is Windows 11, latest patch and 1.0.2. I am unsure if other versions are affected. I only noticed this after loading a larger then usual list. (since that seems to be working now)
Additional Information
The text was updated successfully, but these errors were encountered: