TabbedPage switch page performance problem

voidstreamvoidstream FRMember ✭✭✭
edited February 2017 in Xamarin.Forms

Hello,

I have a tabbedpage and i have "randoms lags" when i switch page. My tabbedpage itemsource is binding with an IGrouping<int,MyClass>>.
Each page got a calendar.

Anyone got an idea?

Best regards

Debug infos after 2 consecutives switch move:

02-21 15:20:05.479 I/art     (11401): Explicit concurrent mark sweep GC freed 3361(161KB) AllocSpace objects, 0(0B) LOS objects, 40% free, 14MB/23MB, paused 960us total 48.639ms
02-21 15:20:05.499 D/Mono    (11401): GC_TAR_BRIDGE bridges 4 objects 634316 colors 4 ignored 381990 sccs 4 xref 0 cache 0/0 setup 0.35ms tarjan 737.16ms scc-setup 0.03ms gather-xref 0.00ms xref-setup 0.00ms cleanup 21.43ms
02-21 15:20:05.499 D/Mono    (11401): GC_BRIDGE: Complete, was running for 78.65ms
02-21 15:20:05.499 D/Mono    (11401): GC_MINOR: (Nursery full) time 825.87ms, stw 826.16ms promoted 42K major size: 33648K in use: 32056K los size: 3072K in use: 1610K
02-21 15:20:05.509 I/Choreographer(11401): Skipped 53 frames!  The application may be doing too much work on its main thread.
02-21 15:20:05.549 D/ViewRootImpl(11401): ViewPostImeInputStage ACTION_DOWN
02-21 15:20:06.169 D/ViewRootImpl(11401): ViewPostImeInputStage ACTION_DOWN
02-21 15:20:06.229 W/ResourceType(11401): Failure getting entry for 0x01080ad1 (t=7 e=2769) (error -75)
02-21 15:20:06.229 W/ResourceType(11401): Failure getting entry for 0x01080ad1 (t=7 e=2769) (error -75)
02-21 15:20:06.229 D/AbsListView(11401): Get MotionRecognitionManager
02-21 15:20:06.239 W/FragmentManager(11401): moveToState: Fragment state for FragmentContainer{2ebfe03f #3 id=0x4 android:switcher:4:537017682} not updated inline; expected state 3 found 2
02-21 15:20:06.839 I/Choreographer(11401): Skipped 35 frames!  The application may be doing too much work on its main thread.
02-21 15:20:10.999 D/Mono    (11401): [0x9288ef80] hill climbing, change max number of threads 19
02-21 15:20:27.859 D/Mono    (11401): [0x9288e300] hill climbing, change max number of threads 5
02-21 15:20:36.889 D/Mono    (11401): [0x9288e300] hill climbing, change max number of threads 4
02-21 15:20:50.079 D/Mono    (11401): [0x91e2ea80] hill climbing, change max number of threads 24
02-21 15:20:51.669 I/art     (11401): Explicit concurrent mark sweep GC freed 3368(167KB) AllocSpace objects, 0(0B) LOS objects, 40% free, 14MB/24MB, paused 969us total 53.228ms
02-21 15:20:51.709 D/Mono    (11401): GC_TAR_BRIDGE bridges 77 objects 638730 colors 77 ignored 382541 sccs 77 xref 0 cache 0/0 setup 0.22ms tarjan 750.92ms scc-setup 0.21ms gather-xref 0.01ms xref-setup 0.00ms cleanup 32.65ms
02-21 15:20:51.709 D/Mono    (11401): GC_BRIDGE: Complete, was running for 91.00ms
02-21 15:20:51.709 D/Mono    (11401): GC_MINOR: (Nursery full) time 847.76ms, stw 848.09ms promoted 323K major size: 34016K in use: 32411K los size: 3072K in use: 1689K
Thread finished: <Thread Pool> #19
02-21 15:20:51.729 I/Choreographer(11401): Skipped 56 frames!  The application may be doing too much work on its main thread.
Le thread 'Unknown' (0x13) s'est arrêté avec le code 0 (0x0).
Thread started: <Thread Pool> #20
Tagged:

Best Answer

  • voidstreamvoidstream FR ✭✭✭
    Accepted Answer

    The application may be doing too much work on its main thread.

Answers

  • voidstreamvoidstream FRMember ✭✭✭
    Accepted Answer

    The application may be doing too much work on its main thread.

Sign In or Register to comment.