-
Notifications
You must be signed in to change notification settings - Fork 119
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
Possible memory leak in Serenity 0.12 and Songbird 0.4. #205
Comments
I've been running my own bot continuously for a day or so which also plays back many small audio files; I'm not seeing my CPU or memory substantially increase over time in a single server. I'll keep you posted if anything changes on that front. |
I don't know if this is directly related to this issue, but after several days of running my application, I am accumulating tasks that never finish. I am not familiar with the structure of serenity or songbird, but it seems that tasks generated by songbird's task.rs and serenity's tokio.rs remain relatively well. |
I need a little more context; one of each |
Thanks for letting me know. if let Some(manager) = songbird::get(ctx).await {
let call_count = manager.iter().count();
} As for the scale of the application, the number of simultaneous VC connections at 30k guilds is about 2k at peak time. |
Songbird version: (version)
0.4.0-rc
Rust version (
rustc -V
): (version)1.74.0
Serenity/Twilight version: (version)
Serenity 0.12.0-rc
Description:
When a large number of small audio files are played back, CPU utilization increases and memory usage explodes after a certain period of time.
Steps to reproduce:
Rust installation is omitted.
!join
on Discord to invite the BOT to the voice channel.It crashes faster if you have it connected to several VCs at the same time.
Verification environment
CPU: ARM Ampere
CPU: 2 core
RAM: 4 GB
OS: Ubuntu 20.04
IaaS: Oracle Cloud Infrastructure
Repositories for verification: https://github.com/abokado0107/tts-memory-leak
The text was updated successfully, but these errors were encountered: