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

100% CPU + Large/Fast Memory Leak #8

Open
3vi1 opened this issue Jan 5, 2021 · 2 comments
Open

100% CPU + Large/Fast Memory Leak #8

3vi1 opened this issue Jan 5, 2021 · 2 comments

Comments

@3vi1
Copy link

3vi1 commented Jan 5, 2021

CasterSoundBoard appears to work. But, randomly it will begin using 100% of one CPU core and then consumes all available memory (32GB). Perhaps something has changed with the newer Qt libraries to make a pre-existing problem more evident?

Basic system details

Qt 5.15.2 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 10.2.1 20201207) on "xcb"
OS: Ubuntu Hirsute Hippo (development branch) [linux version 5.8.0-25-generic]

CasterSoundboard version+commit: v1.0 BETA + commit 1a84315
Operating system: Ubuntu 21.04 (alpha)
Desktop environment: KDE Plasma 5.20.5

Steps to reproduce

  1. Load a couple of soundboard tabs full of small sounds (<5 second wavs and mp3s).
  2. Play random sounds from the boards.
  3. Check CPU and watch memory utilization grow constantly - even when not playing sounds.

High CPU
Growing Memory Utilization

The app will exhaust all memory if left running.

Is this project still maintained? I notice that a lot of issues have been added to the JupiterBroadcasting fork, but that fork doesn't appear to be under development.

@3vi1
Copy link
Author

3vi1 commented Jan 6, 2021

The memory leak is actually worse than I first thought. I just loaded CasterSoundBoard, opened two tabs, and let it sit. It ran out the system out of memory 10 minutes later - without ever playing a sound. So, the leak is not in the playback functions.

@3vi1
Copy link
Author

3vi1 commented Jan 8, 2021

The issue I was experiencing seems to be related to the tab data. I noticed the leak only happened if I loaded one of the two tabs, so I deleted the tab causing issues and created a new one. I've added most sounds back and the problem has not returned.

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

No branches or pull requests

1 participant