https://projects.osmocom.org/https://projects.osmocom.org/favicon.ico?16647414092016-05-22T10:16:37ZOpen Source Mobile Communicationsosmo-gbproxy - Bug #1732: gbproxy: Lifetime of a tracked MS (struct gbproxy_link_info)https://projects.osmocom.org/issues/1732?journal_id=14522016-05-22T10:16:37Zzecke
<ul></ul><p>I wrote a simple script to convert the "write" of the strace (already filtered to be only the leak dump) to make a print of it</p>
<pre>
import sys
with open("talloc_report_strace_gbproxy.txt", "r") as f:
for line in f:
sys.stdout.write(line.split('"')[1].replace("\\n", "\n"))
</pre>
<p>The dump might include sensitive information so let me try to abstract it.</p>
<pre>
$ python strace_to_print.py | grep process_bssgp_ul | wc -l
74428
$ python strace_to_print.py | grep link_info | wc -l
72865
</pre>
<p>I don't think there are that many active users right now and in fact.. looking at</p>
<pre>
show gbproxy links
...
TLLI 9308c247, IMSI (none), AGE 6547738, STORED 3
</pre>
<p>So we have a 75 days old entry.. that has three messages queued. It is unlikely that it will get into another state after that.</p> osmo-gbproxy - Bug #1732: gbproxy: Lifetime of a tracked MS (struct gbproxy_link_info)https://projects.osmocom.org/issues/1732?journal_id=14532016-05-22T10:19:53Zzecke
<ul><li><strong>Subject</strong> changed from <i>gbproxy: Memory leak in the gbproxy?</i> to <i>gbproxy: Lifetime of a tracked MS (struct gbproxy_link_info)</i></li></ul><ul>
<li>The config has <code>link-list max-length 2000</code> but not max-age. The max-length is applied per peer and not globally, so not many peers run into this limit.</li>
<li>gbproxy_remove_stale_link_infos is only called when a link-info is updated, e.g. on a stale/idle peer this will not be updated (after a quick look).</li>
</ul> osmo-gbproxy - Bug #1732: gbproxy: Lifetime of a tracked MS (struct gbproxy_link_info)https://projects.osmocom.org/issues/1732?journal_id=14542016-05-22T10:41:18Zzecke
<ul><li><b>Checklist item</b> <input type='checkbox' class='checklist-checkbox' disabled> <i>Expire gbproxy_link_info on dead links</i> added</li><li><b>Checklist item</b> <input type='checkbox' class='checklist-checkbox' disabled> <i>Periodically expire (on dead NS, etc)</i> added</li></ul> osmo-gbproxy - Bug #1732: gbproxy: Lifetime of a tracked MS (struct gbproxy_link_info)https://projects.osmocom.org/issues/1732?journal_id=17992016-07-12T10:41:28Zlaforge
<ul><li><strong>Assignee</strong> set to <i>fixeria</i></li></ul> osmo-gbproxy - Bug #1732: gbproxy: Lifetime of a tracked MS (struct gbproxy_link_info)https://projects.osmocom.org/issues/1732?journal_id=18012016-07-12T10:43:40Zlaforge
<ul><li><strong>Assignee</strong> changed from <i>fixeria</i> to <i>daniel</i></li></ul> osmo-gbproxy - Bug #1732: gbproxy: Lifetime of a tracked MS (struct gbproxy_link_info)https://projects.osmocom.org/issues/1732?journal_id=66772017-12-10T20:01:45Zlaforge
<ul><li><strong>Project</strong> changed from <i>OpenBSC</i> to <i>OsmoSGSN</i></li></ul> osmo-gbproxy - Bug #1732: gbproxy: Lifetime of a tracked MS (struct gbproxy_link_info)https://projects.osmocom.org/issues/1732?journal_id=66982017-12-10T20:09:52Zlaforge
<ul><li><strong>Category</strong> set to <i>299</i></li></ul> osmo-gbproxy - Bug #1732: gbproxy: Lifetime of a tracked MS (struct gbproxy_link_info)https://projects.osmocom.org/issues/1732?journal_id=82822018-03-16T19:51:08Zlaforge
<ul><li><strong>Assignee</strong> changed from <i>daniel</i> to <i>4368</i></li></ul> osmo-gbproxy - Bug #1732: gbproxy: Lifetime of a tracked MS (struct gbproxy_link_info)https://projects.osmocom.org/issues/1732?journal_id=114352018-09-18T15:48:01Zpespin
<ul><li><b>Checklist item</b> <input type='checkbox' class='checklist-checkbox' checked disabled> <i>Expire gbproxy_link_info on dead links</i> set to Done</li><li><b>Checklist item</b> <input type='checkbox' class='checklist-checkbox' checked disabled> <i>Periodically expire (on dead NS, etc)</i> set to Done</li><li><strong>Status</strong> changed from <i>New</i> to <i>Resolved</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>I was totally unaware of this ticket and I actually arrived to same conclusions and provided fixes for them a while ago.</p>
<p>See following osmo-sgsn commits:<br />82f13612 gbproxy: Add new VTY-managed timer: link-list clean-stale-timer<br />67f1d1ed gbproxy: Add VTY parameter: link stored-msgs-max-length</p> osmo-gbproxy - Bug #1732: gbproxy: Lifetime of a tracked MS (struct gbproxy_link_info)https://projects.osmocom.org/issues/1732?journal_id=181282020-05-01T13:23:23Zlaforge
<ul><li><strong>Project</strong> changed from <i>OsmoSGSN</i> to <i>osmo-gbproxy</i></li><li><strong>Category</strong> deleted (<del><i>299</i></del>)</li></ul>