-
Notifications
You must be signed in to change notification settings - Fork 44
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
Fix memory leakage Tribler.dispersy.candidate.Candidate #442
Comments
How many communities did you have in memory? |
standard testing. When doing 'mp3' search certains objects become big. They nicely disappear with a result list of just a few items. Same for channel browsing. That is all good. These dispersy items never decrease. Slowly grow with each new discovered peers. Standard Tribler default communities. |
After running Tribler for 4 weeks 4 days and 16hours: thousands of objects in memory.
|
Could you start the wx inspectiontool (ctrl+i), and then in the console
|
And the output of the command I posted above? |
hey! @NielsZeilemaker |
The key is only bound in the debug panel, first go there |
And
|
And after
|
checking.. |
trying dowser again.. |
Let's remove the communities one by one.
Not sure how Tribler will respond 😄 And remove them one by one. |
after the unload attempt:
|
|
Thnx Niels! Sadly after 4 weeks Tribler ran out of memory to use. Starting dowser and WX inspection tool surely didn't help. Will try again.
|
Memory was growing a bit, even after 75 of object where removed
After 1 unload:
|
@NielsZeilemaker
Console logfile:
|
So then probably something else is keeping a reference to the candidates. So that would be Tribler. Is there a debug panel which has any lists of candidates? |
we have a small memory leak.
4000 Tribler.dispersy.candidate.Candidate objects are in memory after 30h.
145313 Tribler.dispersy.candidate.Candidate objects are in memory after 784h.
Suspects for memory leakage. Our automatic reports with difficult 60MByte traces: http://jenkins.tribler.org/job/Test_performance_Tribler_idle_24H_nightly_devel/605/artifact/output/memprof/2180/
Elric has some tools parsing this. These can identify the possible dictionary.
Using Dowser we see the following suspects:
Tribler.dispersy.candidate.Candidate
Tribler.dispersy.candidate.WalkCandidate
Tribler.dispersy.member.Member
(probably linked to their key: Tribler.dispersy.crypto.M2CryptoPK)
Tribler shows 1108 channels, Dowser stores
Tribler.Main.Utility.GuiDBTuples.Channel
At 11:00am, after running for 24hours:
![dowser_1100am_dump](https://cloud.githubusercontent.com/assets/325224/8574189/b8d06cd6-2595-11e5-8109-b75330693cdc.png)
8 hours later:
![dowser_1700_dump](https://cloud.githubusercontent.com/assets/325224/8574367/93a3ee32-2596-11e5-9eaa-23a0e28b43d3.png)
The text was updated successfully, but these errors were encountered: