Project

General

Profile

Bug #1803

osmo-bts-litecell15: AMR FR: some RTP buffers are never released

Added by laforge over 1 year ago. Updated about 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
osmo-bts-litecell15
Target version:
-
Start date:
08/20/2016
Due date:
% Done:

100%

Spec Reference:

Description

More details are not yet known, would be great to get more input on this, particularly which buffers (uplink? downlink? msgbs? libortp mbuf?) are leanking and when. talloc_report can help.


Related issues

Related to OsmoBTS - Bug #1802: AMR DTX Downlink: We are not sending ONSET ?!? Closed 08/20/2016
Related to OsmoBTS - Bug #1801: AMR DTX: downlink logic flawed Closed 08/20/2016
Related to OsmoBTS - Bug #1800: AMR DTX: lchan->tch.last_sid is never populated with save_last_sid() Closed 08/20/2016
Related to OsmoBTS - Bug #1799: AMR DTX: last_sid should operate on codec frame intervals (20ms), not gsm frame number Closed 08/20/2016

History

#1 Updated by laforge over 1 year ago

  • Status changed from New to Stalled

#2 Updated by laforge over 1 year ago

  • Related to Bug #1802: AMR DTX Downlink: We are not sending ONSET ?!? added

#3 Updated by laforge over 1 year ago

  • Related to Bug #1801: AMR DTX: downlink logic flawed added

#4 Updated by laforge over 1 year ago

  • Related to Bug #1800: AMR DTX: lchan->tch.last_sid is never populated with save_last_sid() added

#5 Updated by laforge over 1 year ago

  • Related to Bug #1799: AMR DTX: last_sid should operate on codec frame intervals (20ms), not gsm frame number added

#6 Updated by laforge over 1 year ago

  • Assignee changed from sysmocom to msuraev

#7 Updated by msuraev over 1 year ago

  • % Done changed from 0 to 50

Not sure I understood bug correctly, but it might be fixed by gerrit # 1027, 1028.

#8 Updated by msuraev over 1 year ago

  • Status changed from Stalled to Resolved
  • Assignee changed from msuraev to laforge
  • % Done changed from 50 to 100

Gerrit # 1027 & 1028 have been merged. There are no updates to this bug so far - I think we can close it unless some more specific details are available.

#9 Updated by laforge about 1 year ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF