Sure...
Here's the stack trace
java.lang.NullPointerException
at org.red5.server.CoreHandler.connect(CoreHandler.java:77)
at org.red5.server.Scope.connect(Scope.java:391)
at org.red5.server.Scope.connect(Scope.java:388)
at
org.red5.server.BaseConnection.connect(BaseConnection.java:264)
at
org.red5.server.net.rtmp.RTMPConnection.connect(RTMPConnection.java:241)
at
org.red5.server.net.rtmp.RTMPMinaConnection.connect(RTMPMinaConnection.j
ava:67)
at
org.red5.server.net.rtmp.RTMPHandler.onInvoke(RTMPHandler.java:266)
at
org.red5.server.net.rtmp.BaseRTMPHandler.messageReceived(BaseRTMPHandler
.java:143)
at
org.red5.server.net.rtmp.RTMPMinaIoHandler.messageReceived(RTMPMinaIoHan
dler.java:120)
at
org.apache.mina.common.support.AbstractIoFilterChain$TailFilter.messageR
eceived(AbstractIoFilterChain.java:703)
at
org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageRece
ived(AbstractIoFilterChain.java:362)
at
org.apache.mina.common.support.AbstractIoFilterChain.access$1100(Abstrac
tIoFilterChain.java:54)
at
org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.message
Received(AbstractIoFilterChain.java:800)
at
org.apache.mina.filter.executor.ExecutorFilter.processEvent(ExecutorFilt
er.java:247)
at
org.apache.mina.filter.executor.ExecutorFilter$ProcessEventsRunnable.run
(ExecutorFilter.java:307)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecuto
r.java:885)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.ja
va:907)
at java.lang.Thread.run(Thread.java:619)
The caveat to the fix we did is, this only prevents the memory leak, but
does not solve the root of the problem. Perhaps using a harvesting
thread to do the removals will solve it, rather than using
WeakReferences and counting on the vm to do the cleanup? I opened the
ticket in JIRA.
--Adrian
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Joachim Bauch
Sent: Tuesday, July 24, 2007 1:50 PM
To: [email protected]
Subject: Re: [Red5] Memory leak
Hi Adrian,
Roston, Adrian - iFilm schrieb:
> I believe we've found a bug.
[...]
> Which leads to a memory leak. We wrapped this call in a try/catch and
> the problem has gone away.
thanks for pointing this out. Could you please describe a bit more where
the NPE is thrown and in which cases?
Anyway, please create a patch about your try/catch change against the
latest SVN trunk and add a ticket to jira.red5.org so we can fix this
issue.
Joachim
_______________________________________________
Red5 mailing list
[email protected]
http://osflash.org/mailman/listinfo/red5_osflash.org
_______________________________________________
Red5 mailing list
[email protected]
http://osflash.org/mailman/listinfo/red5_osflash.org
