[ 
https://issues.apache.org/jira/browse/OPENMEETINGS-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13509806#comment-13509806
 ] 

Mikael Kurula commented on OPENMEETINGS-270:
--------------------------------------------

Very interesting! Coming to think of it, I think I have also used screen 
sharing every time I got into the loop problem. Now I left out the screen 
sharing and I could record four videos consecutively without ending up in the 
loop.

My clients have been Firefox in OS X 10.6.8 with flash player version 
11.5.502.110. My server is a CentOS 6 with the following software versions:

Name        : ffmpeg
Arch        : x86_64
Version     : 0.6.5
Release     : 1.el6.rf
Size        : 6.9 M
Repo        : installed
>From repo   : rpmforge

java version "1.6.0_37" (Oracle)
Java(TM) SE Runtime Environment (build 1.6.0_37-b06)
Java HotSpot(TM) 64-Bit Server VM (build 20.12-b01, mixed mode)


                
> MemoryLeak / Dead-Lock in FlvRecorderConverter
> ----------------------------------------------
>
>                 Key: OPENMEETINGS-270
>                 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-270
>             Project: Openmeetings
>          Issue Type: Bug
>    Affects Versions: 2.0 Apache Incubator Release
>            Reporter: SebastianWagner
>            Assignee: SebastianWagner
>            Priority: Critical
>             Fix For: 2.1 Apache Incubator Release
>
>
> DEBUG 05-15 16:08:19.955 FlvRecorderConverter.java 113480470 96 
> org.openmeetings.app.data.flvrecord.converter.FlvRecorderConverter 
> [taskExecutor-4] - ### Stream not yet written Thread Sleep -
> => The Thread does sleep endlessly. We need to find out what causes that 
> error and how we can prevent it.
> First of all a more detailed trace is needed to identify those recording_Ids 
> that are broken to try to find out what happened and how long the Converter 
> hands in the loop.
> It can be criticial if it turns out that there is a general issue with the 
> recording there.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to