Neil Stevenson wrote:
> Hi Greg,
> 
> Ok, I've tried http/mp3 playback and it seems a lot cleaner - the
> HXClientEngine and HXPlayer seem to be release and deleted OK. The
> CHXMediaPlatform is still leaked.  
> 
> On RTSP, I also notice that sometimes a second CHXMediaPlatform object is
> created and this is leaked also.  This is created in the plugin iteration
> loop in the rtsp client.  This could be when the UDP connection falls back
> to TCP, as UDP is unreliable through our router...

what branch are you on? For Atlas, the rtsp code has been pulled out
into a new DLL, that is one thing to keep in mind.

--greg.


> 
> Cheers,
> Neil.
> 
> -----Original Message-----
> From: Greg Wright [mailto:gwright at real.com] 
> Sent: 21 March 2007 17:10
> To: neil.stevenson at frontier-silicon.com
> Cc: helix-client-dev at helixcommunity.org
> Subject: Re: [Helix-client-dev] Reference Count problem with splay
> 
> Neil Stevenson wrote:
>> Hi Greg,
>>
>> Thanks for the reply.
>> I only have Audio support in my build, no Video plug-ins are included.
>> Also, we've stubbed out all of the local file support (not needed on our
>> platform), so I can't easily try a local playback.  I'll see if I can add
> it
>> back in and try it.  I am seeing the problem over RTSP, but it could be
> more
>> general.
> 
> How about HTTP then? I am just trying to narrow down the leak as much
> as possible because these are not easy to find. I am also wondering if
> somehow the removal of the local playback support is a problem. I say
> that only because it is not a very common setup and so a leak might
> have been missed.
> 
>> I'm trying to add further debug in at the moment - I'll try and give you
>> more info when I know more...
> 
> Ok, cool.
> 
> 
> --greg.
> 
>> Cheers,
>> Neil.
>>
>> -----Original Message-----
>> From: Greg Wright [mailto:gwright at real.com] 
>> Sent: 21 March 2007 16:52
>> To: neil.stevenson at frontier-silicon.com
>> Cc: helix-client-dev at helixcommunity.org
>> Subject: Re: [Helix-client-dev] Reference Count problem with splay
>>
>> Neil Stevenson wrote:
>>> Hi,
>>>
>>> I seem to be having a reference count problem with the player when it
>> stops
>>> playing, resulting in a memory leak.   In our limited-memory system, this
>>> means we eventually run out of memory.  We have modelled our player on
> the
>>> splay code, creating a new engine, player etc. each time the player is
>>> started.  We have no automatic operating system freeing of memory.
>>>
>>> If I build splay.exe from the head branch on Windows, then play a single
>>> RTSP RealAudio stream, all is OK until I tell splay to quit.  On exit, I
>>> find that the HXPlayer still has a reference count of 6, HXMediaPlatform
>> has
>>> 10, and HXClientEngine has 1.   I don't seem to be able to get them to
>> zero.
>>> If I play a RAM file, then the counts are even higher, so I suspect it's
>> the
>>> RTSP Client code somewhere.
>>>
>>>  
>>>
>>> Is this a known problem on the Head (Atlas) code?  Anyone else seen this?
>> This is not a know problem that I know of.
>>
>>
>> Does this happen if you play local files?
>> Does this happen with audio only and/or video only?
>> Does this happen if you play local video?
>>
>> I would also be interested to know what happens to the ref counts
>> if you force an extra release on the HXClientEngine, since you
>> have a handle to it. That would tell us how many of the other
>> refs might be held by the engine itself.
>>
>>
>> --greg.
>>
> 
>