[Red5devs] One Critical Memory Leak Issue Fixed on Trunk (r2645)

[SeTyR]

Sorry for my last post;
I found the "trunk tracker"

Can i just download it and simply ant server & ? 
what's the most convenient way to update red5 on my server say on a weekly basis  ?

i just don't want to loose some tweakings in my app and files and some outer-directory reading tweaks stuffs :/

Thanks again !
SeTyR

  ----- Original Message ----- 
  From: SeTyR 
  To: red5devs at osflash.org 
  Sent: Thursday, February 14, 2008 4:24 AM
  Subject: Re: [Red5devs] One Critical Memory Leak Issue Fixed on Trunk (r2645)


  Hi Steve and Lenny;  

  As i am not good at all at java, but really slowly beginning ..; i might be asking something really basic but i'll ask it anyway as the only thing i can and know how to do is altering scripts and testing, altering and testing .. ^^

  Where can i find that "CallerRunsPolicy" (function?), and how do i "set the CallerRunsPolicy to the executor"  ? 

  I suspect my red5 server has sometimes a memory problem, this might solve that ?

  Also , concerning H264 and stuff,  if you guys need a video ripper/encoder guy for any bw/vp6/h264 test purposes , i'm willing to give time for that  

  Thanks for reading 
  Thanks again for Red5

  SeTyR
    ----- Original Message ----- 
    From: Lenny Sorey 
    To: red5devs at osflash.org 
    Sent: Thursday, February 14, 2008 3:41 AM
    Subject: Re: [Red5devs] One Critical Memory Leak Issue Fixed on Trunk (r2645)


    Thanks Steve,

    Lenny

     
    On 2/13/08, Steven Gong <steven.gong at gmail.com> wrote: 
      Hi all,
      I just checked in the fix for a critical memory leak bug which is caused by MINA ExecutorFilter. MINA will cache the event packets into an internal buffer before handing them off to the working threads in ExecutorFilter. When the Executor can't provide enough working threads for the event packet, an exception will be thrown by default and the IoSession the generates the event packet will be marked as "working" which prevents other threads to handle on it. Thus more event packets will be added in the internal buffer but no thread will remove and handle them -- memory leaks.

      To avoid this, I . As this is a critical bug, I also CCed to the user list for information.

      -- 
      Best Regards
      Steven Gong

      InfraRed5 Red5 Consultant: http://www.infrared5.com, steven at infrared5.com

      Red5 Developer: http://osflash.org/red5, http://jira.red5.org/confluence/display/~steven/Home

      Javaflash Project Founder and Maintainer: http://osflash.org/javaflash

      Modesty is an overrated quality in men of no great accomplishment.  -- Ricky Jay 
      _______________________________________________
      Red5devs mailing list
      Red5devs at osflash.org
      http://osflash.org/mailman/listinfo/red5devs_osflash.org






----------------------------------------------------------------------------


    _______________________________________________
    Red5devs mailing list
    Red5devs at osflash.org
    http://osflash.org/mailman/listinfo/red5devs_osflash.org



----------------------------------------------------------------------------


    No virus found in this incoming message.
    Checked by AVG Free Edition. 
    Version: 7.5.516 / Virus Database: 269.20.4/1275 - Release Date: 12/02/2008 15:20



------------------------------------------------------------------------------


  _______________________________________________
  Red5devs mailing list
  Red5devs at osflash.org
  http://osflash.org/mailman/listinfo/red5devs_osflash.org



------------------------------------------------------------------------------


  No virus found in this incoming message.
  Checked by AVG Free Edition. 
  Version: 7.5.516 / Virus Database: 269.20.4/1275 - Release Date: 12/02/2008 15:20
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://osflash.org/pipermail/red5devs_osflash.org/attachments/20080214/ff6c51b4/attachment.html