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

[Steven Gong]

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 set the CallerRunsPolicy to the executor. 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://osflash.org/pipermail/red5devs_osflash.org/attachments/20080214/a36af4d2/attachment.html