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

[GetDocs] Regular CPU spike when cog has been loaded. #55

Open
madebylydia opened this issue Jul 5, 2024 · 0 comments
Open

[GetDocs] Regular CPU spike when cog has been loaded. #55

madebylydia opened this issue Jul 5, 2024 · 0 comments
Assignees
Labels
bug Something isn't working wontfix This will not be worked on

Comments

@madebylydia
Copy link

madebylydia commented Jul 5, 2024

What cog is this bug report for?

GetDocs

Describe the bug

The cog GetDocs has an alarming CPU spike usage when loaded.

The following is a representation of the bot's process when the cog is loaded

Process's usage **with** cog

image

image

Process's usage **without ** cog

image

This is extremely abnormal and should be fixed, considering the process usage can spike up to 100%.

Worse, those spikes are persisting across cog's unloading and uninstallation.
Restarting the bot fix the problem.

I confirm having realized enough research to conclude that the cog GetDocs is the problematic cog, and no other cogs are entering in conflict.

If there's an error, paste it here

No response

@madebylydia madebylydia changed the title Regular CPU spike using cog [GetDocs] Regular CPU spike when cog has been loaded Jul 5, 2024
@AAA3A-AAA3A AAA3A-AAA3A changed the title [GetDocs] Regular CPU spike when cog has been loaded [GetDocs] Regular CPU spike when cog has been loaded. Aug 24, 2024
@AAA3A-AAA3A AAA3A-AAA3A self-assigned this Aug 24, 2024
@AAA3A-AAA3A AAA3A-AAA3A added bug Something isn't working wontfix This will not be worked on labels Aug 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants