search

red5pro / streaming-ios

This repository contains a simple project with a number of iOS examples that can be used for testing and reference.
Other
92 stars 29 forks source link

[R5 WARNING] Error closing main loop: resource busy or locked #91

Open starcoach opened 7 years ago

starcoach commented 7 years ago

We are building a 2-way 2 streams video education app using Red5pro. Our iOS app worked fine on SDK 3.1.0.

When we upgraded to SDK 3.4, 2 streams feature stopped working, viewers cannot see the second stream, and we get error on second stream: [R5 WARNING] Error closing main loop: resource busy or locked

We tried your sample app, again, 2 way, 2 streams, and 2nd screen feature do not work on SDK 3.4. we cannot see the second stream.

We host Red5pro server on Ubuntu at Digital Ocean.

-Michael

dangdinhquan commented 7 years ago

we got the same issue too. Please help!!!

beetlejesss commented 7 years ago

@showbucks2012 @dangdinhquan - Please enter a ticket in https://red5pro.zendesk.com/hc/en-us/requests/new with full details, including your iOS version and server version. I verified that I could run the two-way example on iPhone7 (iOS 10.2.1) and iPhone 6s (iOS 10.2.1 and also iOS 9.3.1). thanks

VivekGoswami commented 7 years ago

I am using in iOS 10.3 with swift 3 when run on device and goes to publish the streaming not send to server and also subscribe not working in device only black screen comes and crash with [R5 WARNING] Error closing main loop: resource busy or locked. but works in Simulator. @beetlejesss . Please help!

HoldenMills commented 7 years ago

Hello Vivek,

Could you please fill out a support ticket? Please include your red5.log file along with your device logs. For instructions on how to do that, please follow this FAQ. The Warning that you are seeing may not be a fatal error and your issue could be from something else.

Cheers, Holden

VishadPatel commented 7 years ago

Hi Team,

My Team is also facing same issue in the publish & subscriber user case. Currently we are using iOS 3.5 SDK for development. This issue is not happening frequently but come few time during testing.