App stucked when swiping fast back and forth from two CNViewControllers

[Perjan]

I have an app which has 2 subclasses of the CNViewController. One of these has a container view controller. And when I swipe fast between them, the main thread seems to be blocked, and after 2-3 seconds it goes back to the swiped view controller.

[artemstepanenko]

Thanks for letting me know about the problem.
At this point it's hard to say what might cause the problem. Could you please press pause when it's stuck and paste here the stack trace? Or whatever, you think, is a reason of the problem. Thanks.

[Perjan]

Hey Artem,
thanks man.
I will test it today and send you the stack trace.

Cheers,
P

On 16 Sep 2015, at 15:23, Artem Stepanenko notifications@github.com wrote:

Thanks for letting me know about the problem.
At this point it's hard to say what might cause the problem. Could you please press pause when it's stuck and paste here the stack trace? Or whatever, you think, is a reason of the problem. Thanks.

—
Reply to this email directly or view it on GitHub #24 (comment).

[artemstepanenko]

Hi Perjan, thank you too.

[Perjan]

Hey Artem,
how are you?
I got the stack trace. You can find it attached here.

On my main screen I have a content view that has an embedded custom AVFoundation camera.
I have one UITableViewController on the right and one on the left.
Now, when I switch too fast, the app stop responding and also the UIButtons that are on the MainVC don’t get any press events.
I noticed the same behaviour when the app becomes active again.

Please help me with this and let me know if you need more info.

Cheers,
P

On 16 Sep 2015, at 15:23, Artem Stepanenko notifications@github.com wrote:

Thanks for letting me know about the problem.
At this point it's hard to say what might cause the problem. Could you please press pause when it's stuck and paste here the stack trace? Or whatever, you think, is a reason of the problem. Thanks.

—
Reply to this email directly or view it on GitHub #24 (comment).

[artemstepanenko]

Perjan, you sent me more details about your app. This may help.
But what would be super-useful is a stack trace (which I haven't found in your previous message). I need to know a sequence of calls which stops the UI-thread. Thanks.

[Perjan]

Ah, sorry, the file didn't get attached. Still:

Running Time,Self (ms),,Symbol Name
225.0ms 83.0%,0, ,Main Thread 0x1a670
105.0ms 38.7%,0, , main
62.0ms 22.8%,0, , -[CNViewController panGestureHandler:didStartForDirection:]
62.0ms 22.8%,0, , -[CNPanGestureHandler notifyDelegateAboutStart]
45.0ms 16.6%,0, , -[CNInteractiveTransition startInteractiveTransition:]
45.0ms 16.6%,0, , main
2.0ms 0.7%,0, , -[CNViewController initWithCoder:]
1.0ms 0.3%,1, , 0x1913a8180
1.0ms 0.3%,0, , -[CNViewController createNextViewControllerForDirection:]
1.0ms 0.3%,1, , 0x1992bf340
1.0ms 0.3%,1, , 0x189747840
1.0ms 0.3%,0, , 0x64001b
1.0ms 0.3%,1, , 0x1913a73cc
1.0ms 0.3%,1, , 0x1913a7758
1.0ms 0.3%,1, , -[ParseManager coreManager]
1.0ms 0.3%,0, , -[CNViewController initializePanGestureRecognizer]
1.0ms 0.3%,0, , -[PFObjectSubclassInfo _rawPropertyInfoForSelector:]
1.0ms 0.3%,1, , 0x1913a72e4

[artemstepanenko]

That's better. I'll try to manage by Monday.

[Perjan]

Thanks man, you’re awesome!

On 17 Sep 2015, at 23:49, Artem Stepanenko notifications@github.com wrote:

That's better. I'll try to manage by Monday.

—
Reply to this email directly or view it on GitHub #24 (comment).

[artemstepanenko]

@Perjan , sorry for a late response. I don't know what might be a reason of this problem, so far. If you could provide any additional information, I would appreciate that.

[vshilman]

Hi, I have the same issue as Perjan. For me this happens in the MainController (Non-Storyboards) on the real device and not simulator. While the dragging works without any issues between left, right top and bottom controllers, the issue i think is in the "sloppy quick swipe".