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

[BUG/ISSUE] High memory usage #1078

Closed
mboop127 opened this issue Jan 4, 2023 · 12 comments
Closed

[BUG/ISSUE] High memory usage #1078

mboop127 opened this issue Jan 4, 2023 · 12 comments
Labels
bug Something isn't working ready-to-go Ready to be fixed without further conversation

Comments

@mboop127
Copy link

mboop127 commented Jan 4, 2023

When left running for a while, elevenclock eventually balloons to 1-3 mb of ram. I saw a similar bug reported earlier but it was marked resolved.

I do regularly leave programs running (python scripts etc) overnight that cause windows explorer to bug out, so it's possible that elevenclock is just reacting to that, but I would appreciate it if you could investigate.

@mboop127 mboop127 added bug Something isn't working triage This hasn't been chcked yet by any maintainer labels Jan 4, 2023
@marticliment
Copy link
Owner

do you mean 1-3gb, right?

has this issue happened again?
if so, can you please try resetting ElevenClock?

@marticliment marticliment added needs-author-answer Waiting for the author to answer. If author does not answer in 2 days, Issue gets closed and removed triage This hasn't been chcked yet by any maintainer labels Jan 4, 2023
@mboop127
Copy link
Author

mboop127 commented Jan 4, 2023

yes gb sorry. It happens eventually after every program or system restart.

@marticliment
Copy link
Owner

can you please share your log after this issue happening?

@marticliment
Copy link
Owner

Hi, could you please try the new beta?
https://github.com/marticliment/ElevenClock/releases/tag/4.0.0-beta1

@mboop127
Copy link
Author

mboop127 commented Jan 5, 2023

image
here is a screenshot - could you walk me through sending you the log? or do you just want me to try the beta?

@marticliment
Copy link
Owner

so, please first install the beta.

if the issue persists, please:

  1. without quitting ElevenClock, open the settings window
  2. Scroll down to "debugging info" and click on that section
  3. A pop-up will show up. Then choose the "Open log" entry
  4. Export the log as a text file and attach it here.

Thanks!

@mboop127
Copy link
Author

mboop127 commented Jan 7, 2023

The update did not resolve the issue, was using 1.1gb of ram when I opened settings to export the log, though once I opened settings usage went back to 100mb or so. Log attached
log.txt

@marticliment
Copy link
Owner

On your user home directlry there's a folder called .elevenclock.

Could you please compres it and send it back to me?

@mboop127
Copy link
Author

mboop127 commented Jan 8, 2023

attached
.elevenclock.zip

@marticliment marticliment added ready-to-go Ready to be fixed without further conversation and removed needs-author-answer Waiting for the author to answer. If author does not answer in 2 days, Issue gets closed labels Jan 8, 2023
@hoekbrwr
Copy link

It looks like there are major memory leaks in the program. Memory usage starts with 65MB and then keeps on rising with every action you do, like reload clocks. If you regularly sync the time on the internet this can reach 1 GB in a day easily.
Have a look at the structure to identify these leaks. Google for the general causes and have an aerial view of your program's structure. It seems to be at a high level in the program because lots of actions make the memory usage rise. Good luck with that!
I however like the program with its many settings. I now know why there is a menu point "reload the program" lol

@marticliment
Copy link
Owner

I am aware of this rises, but I have never experienced those crazy levels of ram.
The issue is still being investigated, but under normal usage without mnessing with the settings, the ram should not rise at all

@marticliment
Copy link
Owner

Next version of ElevenClock includes a new set of improvements that should prevent this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working ready-to-go Ready to be fixed without further conversation
Projects
None yet
Development

No branches or pull requests

3 participants