-finishwriting should not be called on the main thread

Ask questions about the iOS API here

-finishwriting should not be called on the main thread

Postby ras550 » Tue Oct 16, 2012 7:55 am

I am getting this error when the opentok session initializes. I am also getting the following error and crash occasionally on calling OTPublisher initWithDelegate. I am running iOS6 on the New iPad. Anyone else notice this?

/TPCircularBuffer.c:69: Map buffer memory: (os/kern) no space available
Was this post helpful? (0)
ras550
 
Posts: 37
Joined: Mon May 14, 2012 8:20 am
Thumbs Up: 0

Re: -finishwriting should not be called on the main thread

Postby steve » Wed Oct 17, 2012 4:36 pm

Are you getting any out of memory errors in your application?
Was this post helpful? (0)
steve
 
Posts: 33
Joined: Thu Dec 15, 2011 4:33 pm
Thumbs Up: 5

Re: -finishwriting should not be called on the main thread

Postby ras550 » Sun Oct 21, 2012 9:32 am

steve wrote:Are you getting any out of memory errors in your application?


I am getting memory warnings occasionally. The Map buffer memory error I quoted below happens on calling OTPublisher initWithDelegate.
Was this post helpful? (0)
ras550
 
Posts: 37
Joined: Mon May 14, 2012 8:20 am
Thumbs Up: 0

Re: -finishwriting should not be called on the main thread

Postby ras550 » Tue Oct 23, 2012 9:44 am

I am getting this warning "WARNING: -finishWriting should not be called on the main thread." whenever my app ends an opentok session. I am not using it anywhere in my code and the only AV related sdk I have is opentok. Could you confirm that you are using this in your sdk, and if so, any pointers on getting rid of this warning? Thanks very much.
Was this post helpful? (0)
ras550
 
Posts: 37
Joined: Mon May 14, 2012 8:20 am
Thumbs Up: 0

Re: -finishwriting should not be called on the main thread

Postby charley » Tue Oct 23, 2012 10:01 am

It's us; we'll have it gone in the next release.
Was this post helpful? (0)
charley
 
Posts: 364
Joined: Fri May 06, 2011 7:41 pm
Thumbs Up: 28

Re: -finishwriting should not be called on the main thread

Postby ras550 » Tue Oct 23, 2012 10:32 am

charley wrote:It's us; we'll have it gone in the next release.


Thanks Charley. When do you expect the new release to be out?
Was this post helpful? (0)
ras550
 
Posts: 37
Joined: Mon May 14, 2012 8:20 am
Thumbs Up: 0

Re: -finishwriting should not be called on the main thread

Postby charley » Tue Oct 23, 2012 10:35 am

I can't speak officially, but you will probably see it within a week or two on github. I'll update the thread as soon as it's done.
Was this post helpful? (1)
charley
 
Posts: 364
Joined: Fri May 06, 2011 7:41 pm
Thumbs Up: 28

Re: -finishwriting should not be called on the main thread

Postby ras550 » Tue Oct 23, 2012 10:46 am

ok. Do you think there might concerns with submitting an app with this warning to Apple? We plan to submit within the next week.
Was this post helpful? (0)
ras550
 
Posts: 37
Joined: Mon May 14, 2012 8:20 am
Thumbs Up: 0

Re: -finishwriting should not be called on the main thread

Postby charley » Tue Oct 23, 2012 3:39 pm

I honestly don't know, but it would surprise me if this was an issue. Please keep me posted if anything interesting happens.
Was this post helpful? (0)
charley
 
Posts: 364
Joined: Fri May 06, 2011 7:41 pm
Thumbs Up: 28

Re: -finishwriting should not be called on the main thread

Postby ras550 » Tue Nov 06, 2012 1:26 am

Any updates on a new release of the SDK, with this issue fixed?

I also noticed that while analyzing our app using the Leaks Instruments, opentok is responsible for a bunch of leaked objects (related to AVAssetWriter among others). Is this something you have looked into?
Was this post helpful? (0)
ras550
 
Posts: 37
Joined: Mon May 14, 2012 8:20 am
Thumbs Up: 0

Next

Return to iOS



Who is online

Users browsing this forum: No registered users and 2 guests

cron