The "ReorderingPacketBuffer" is not a 'memory leak'. *Every* incoming packet
that gets added to this queue will later get consumed, and its memory will then
get reclaimed (perhaps reused for the next incoming packet). If an incoming
packet weren't added to the "ReorderingPacketBuffer", then it
Because of this suspicion, I ran without the tool at very low resolutions
and used windows' right-click mini-dump feature. I then post processed
these dumps and found the same exact objects, the 68 byte BufferPacket
structure and the 10k BufferPackets growing. Surprisingly they are not in
lock step
>If I let the app run for over a day a slow growth of memory usage occurs.
> This is what I am trying to solve. When I connect the Memory Tool, there are
> no BufferPackets at all. After a few hours, there are a few hundred or a few
> thousand based on how many streams are connected. We qui
I have a strange problem showing up while trying to solve a memory leak
elsewhere in my code. When I attach a memory tool it somehow messes timing
or something and live555 begins to create BufferPacket structures of 68
bytes with a payload of 10K. Somehow they are not released so the code to
ge
