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

Memory leak and high CPU load #3406

Open
thejustsoul opened this issue May 2, 2018 · 9 comments

Comments

Projects
None yet
5 participants
@thejustsoul
Copy link

commented May 2, 2018

During operation, memory leaks (up to 700+ MB) and the processor is heavily loaded (~5-10% at 3.4 GHz), in version 1.2.19 the processor is loaded less than 2%. Positional sound off.. Voice activation by button.

OS Windows 8.1 x64, Mumble 1.3.0~2729~g2126495~snapshot x64

A memory leak screenshot is attached..
screenshot

@thejustsoul

This comment has been minimized.

Copy link
Author

commented May 3, 2018

Perhaps a random bug or conflict with something, at the moment the memory is not leaked. But it's not all right. May be due to the fact that yesterday was not available mumble.info (ssl certificate did not match the domain name) and something happened inside mumble and the memory started to leak?

screenshot

@daborbor

This comment has been minimized.

Copy link

commented May 3, 2018

@i've tested with an entry in my hosts file which point mumble.info to the Reddit IP (151.101.1.140 mumble.info). I've tested over a period of 21 minutes. Where 15 of the 21 minutes I was talking with someone on mumble. The CPU (i5 4460) util stayed 1%< most of the time and the memory usage was 34,9 MB at the end. So a faulty answer from the mumble.info domain doesn't seem to be a problem on my PC. I tested it on mumble 1.3.0~2729~g2126495~snapshot and windows WinX64 (Windows 10 Pro x64 1709 16299.371).

@thejustsoul

This comment has been minimized.

Copy link
Author

commented May 3, 2018

@daborbor Where mumble loads the message in the chat window:
1.3.0 Snapshot Welcome to the Mumble snapshots. Current testing focus is: Features and fixes
On the day when the memory of this inscription was not displayed and did not work checking for new versions (because of what I figured that it somehow connected with mumble.info). Maybe it just coincided ..

@daborbor

This comment has been minimized.

Copy link

commented May 3, 2018

It shouldn't be able to connect to mumble.info but it still can check wether there's an update. We could check to source code to see how it checks for an update. I suppose it connects to GitHub. Maybe we could try to disable our internet access and connect to a server on localhost to test if it has anything to do with not being able to reach a server. It's 00:36 here now so I'm not able to check it right now unfortunately.

@daborbor

This comment has been minimized.

Copy link

commented May 3, 2018

Do you use who cancelation?
You should check this issue #3379
It could maybe be related to this too #2786

@thejustsoul

This comment has been minimized.

Copy link
Author

commented May 4, 2018

Option "echo cancellation" does not use (disabled).
For test, im search in source code Mumble address for check update and found: https://update.mumble.info/v1/banner/
Add to windows hosts reddit ip (as simulation error certificate):
151.101.65.140 update.mumble.info
And run mumble. Mumble load CPU at 15-20% (online server one person) and.. what is (another coincidence)?

screenshot

Another run. After clear hosts and purge dns cache, Mumble show banner, say "version is up to date" and CPU load change to ~1-2%. Then im again change hosts to fake ip, and start checking for updates several times.. result:

screenshot

@daborbor

This comment has been minimized.

Copy link

commented May 4, 2018

I've tested it with 127.0.0.1 update.mumble.info first, after a period of 14 minutes it didn't seem like anything was happening. My CPU (i5 4460) usage stayed 2%< most of the time. I ended the test with 29,3 MB of memory used.
Then I tested it with 151.101.65.140 update.mumble.info. I started with 27 MB of memory usage, buy my CPU (i5 4460) usage skyrocketed. It was 7-11% for the first minute. Then it started fluctuating between 7-8%. After 14 minutes the mumble memory usage increased a lot. It was 68,3 MB when I ended my test. Definitely something going on here.
The network usage was 3-4Mbps. I was talking with one friend. While normally my network usage would be 0-0,2 Mbps in the same circumstances. So there's a lot of network connectivity going on.

@Kissaki

This comment has been minimized.

Copy link
Member

commented May 11, 2018

Note that you can use 0.0.0.0 as an IP address that is invalid and always unreachable.

Thank you for your analysis so far. This gives a pretty clear pointer of where/what to look for.

@Two-Tone

This comment has been minimized.

Copy link

commented Jan 29, 2019

I can attest that there is a memory leak. I'm on Windows 7 x64 and will keep Mumble open for days or weeks at a time, only to be forced to close it as it eventually uses gigs of my ram.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.