Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

60GB RAM after 20s of Streaming #161

Closed
morbificagent opened this issue Jul 28, 2020 · 8 comments
Closed

60GB RAM after 20s of Streaming #161

morbificagent opened this issue Jul 28, 2020 · 8 comments
Labels
bug Confirmed as bug

Comments

@morbificagent
Copy link

Hi @ all,
I was testing OME with an hardware h264 streaming-device which sends to ome via rtmp and ome was exploding ;-)

It was consuming more and more ram and the whole server became problems as ome was using 60GB ram after 20s of the stream... Does anyone had such a problem before?

Streaming from OBS is working without a problem.

And what log-files would you need to take a look on this problem?

@getroot
Copy link
Sponsor Member

getroot commented Jul 28, 2020

Which H264 hardware streaming device do you use? Perhaps there is a problem with the compatibility of the RTMP protocol. (I have recently received a report on it.) We are going to look at this in depth.

@getroot
Copy link
Sponsor Member

getroot commented Jul 28, 2020

After the problem has been reproduced, upload the /var/log/ovenmediaengine/ovenmediaengine.log file. It will help us.

@morbificagent
Copy link
Author

@getroot It is the AVC-2K from www.ddmalltech.com
I will try to reproduce this and send you the logs...

@getroot
Copy link
Sponsor Member

getroot commented Jul 28, 2020

It seems very useful equipment. We will also buy it for use at the exhibition and see why it is not compatible with OME.
(This year the event was canceled with COVID19, but we started participating in NAB and IBC from 2019.)

@morbificagent
Copy link
Author

Yes its really useful as you can preconfigure the streaming url, take it with you, plug it in and your stream is up and running :-) And no software which can crash or windows clients which want to update when you need the stream ;-)

@getroot
Copy link
Sponsor Member

getroot commented Aug 3, 2020

We purchased the equipment you gave us.
This is Seoul (Korea), so it will take a long time to receive equipment. When we receive the equipment, we will analyze the problem.

@getroot getroot added the bug Confirmed as bug label Aug 3, 2020
@dimiden
Copy link
Member

dimiden commented Aug 24, 2020

@morbificagent
Finally we got this equipment, and we found the cause.
I analyzed the RTMP timestamp sent by this device and corrected something wrong in OME's algorithm. (1592695)

I hope this modification works fine.

@morbificagent
Copy link
Author

Many thanks :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Confirmed as bug
Projects
None yet
Development

No branches or pull requests

3 participants