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

mega-cmd-server starts consuming 100% cpu when idle for a long time after several sleep cycles #992

Open
debasish-raychawdhuri opened this issue Aug 1, 2024 · 2 comments
Labels

Comments

@debasish-raychawdhuri
Copy link

MEGAcmd version

1.7.0

Operating System/Platform

Linux

Platform version. In the case of Linux, please enter the Linux distribution you are using.

Garuda Linux (Arch derivative) rolling release

Steps

  1. start mega-cmd-server directly or by invoking mega-cmd
  2. wait for a few hours while going through several sleep cycles
  3. If you are unlucky enough, it starts consuming 1 CPU thread completely like in some spin-lock
  4. restarting mega-cmd-server fixes it until a few more hours and sleep cycles have passed

Expected behavior

mega-cmd-server should consume minimal CPU when idle (nothing to sync)

Actual behavior

mega-cmd-server consumes one CPU-thread completely.

@debasish-raychawdhuri
Copy link
Author

Could reproduce it rather quickly with --debug option. Attached the log
[
mega-cmd-server.log
](url)

@debasish-raychawdhuri
Copy link
Author

I am running it in verbose mode for a day now and the problem did not show up yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant