Page 1 of 2 12 LastLast
Results 1 to 10 of 15

Thread: Frequent crashes in production when exiting app

  1. #1
    Neuer skobbler
    Join Date
    18.10.2016
    Posts
    8

    Frequent crashes in production when exiting app

    We're seeing quite high crash rates with our app in production on iOS. We're using the latest 3.0.2 SDK. The good news is this crash seems to be on exiting the app so users may not see it, but it still shouldn't crash. Unfortunately we have no idea where this originates or what causes this, anyone seeing anything similar or have an idea what causes this.

    PHP Code:
    #0. Crashed: com.apple.main-thread
    0  libsystem_kernel.dylib         0x182a57014 __pthread_kill 8
    1  libsystem_pthread
    .dylib        0x182b1f450 pthread_kill 112
    2  libsystem_c
    .dylib              0x1829cb400 abort 140
    3  libsystem_malloc
    .dylib         0x182a8d944 szone_size 658
    4  libc
    ++.1.dylib                 0x18247a7e8 std::__1::basic_string<charstd::__1::char_traits<char>, std::__1::allocator<char> >::~basic_string() + 32
    5  SKMaps                         0x1011ed7a8 std
    ::__1::__shared_ptr_pointer<TxgPackageInfoWrapper*, std::__1::default_delete<TxgPackageInfoWrapper>, std::__1::allocator<TxgPackageInfoWrapper> >::__on_zero_shared() + 36
    6  libsystem_pthread
    .dylib        0x182b1f450 pthread_kill 112
    7  libc
    ++.1.dylib                 0x182478b5c std::__1::__shared_weak_count::__release_shared() + 60
    8  SKMaps                         0x1011ed384 std
    ::__1::shared_ptr<TxgPackageInfoWrapper>::~shared_ptr() + 28
    9  libsystem_c
    .dylib              0x1829cbff0 __cxa_finalize_ranges 392
    10 libsystem_c
    .dylib              0x182975390 exit + 24
    11 UIKit                          0x1899ca7fc 
    +[_UIAlertManager hideAlertsForTermination] + 490
    12 UIKit                          0x189bcc7cc __102
    -[UIApplication _handleApplicationDeactivationWithScene:shouldForceExit:transitionContext:completion:]_block_invoke.2100 792
    13 UIKit                          0x189bcffdc _runAfterCACommitDeferredBlocks 
    292
    14 UIKit                          0x189bc1d50 _cleanUpAfterCAFlushAndRunDeferredBlocks 
    560
    15 UIKit                          0x1899310b4 _afterCACommitHandler 
    168
    16 CoreFoundation                 0x183a360c0 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ 
    32
    17 CoreFoundation                 0x183a33cf0 __CFRunLoopDoObservers 
    372
    18 CoreFoundation                 0x183a34180 __CFRunLoopRun 
    1024
    19 CoreFoundation                 0x1839622b8 CFRunLoopRunSpecific 
    444
    20 GraphicsServices               0x185416198 GSEventRunModal 
    180
    21 UIKit                          0x1899a97fc 
    -[UIApplication _run] + 684
    22 UIKit                          0x1899a4534 UIApplicationMain 
    208 

  2. #2
    Erfahrener skobbler
    Join Date
    12.09.2016
    Posts
    112
    It seems to be a Core issue.
    I've reported the issue to our dev team for further investigation.

  3. #3
    Neuer skobbler
    Join Date
    05.05.2016
    Posts
    3
    I have the same crashes, but I can't catch the moment when it happens. In Fabric Crashlytics we have so many crash reports with SKMaps.

    Code:
    #0. Crashed: com.apple.main-thread
    0  libsystem_kernel.dylib         0x1894e3014 __pthread_kill + 8
    1  libsystem_pthread.dylib        0x1895ab450 pthread_kill + 112
    2  libsystem_c.dylib              0x189457400 abort + 140
    3  libsystem_malloc.dylib         0x189519944 szone_size + 658
    4  libc++.1.dylib                 0x188f067e8 std::__1::basic_string, std::__1::allocator >::~basic_string() + 32
    5  SKMaps                         0x100af1794 std::__1::__shared_ptr_pointer, std::__1::allocator >::__on_zero_shared() + 36
    6  libsystem_pthread.dylib        0x1895ab450 pthread_kill + 112
    7  libc++.1.dylib                 0x188f04b5c std::__1::__shared_weak_count::__release_shared() + 60
    8  SKMaps                         0x100af1370 std::__1::shared_ptr::~shared_ptr() + 28
    9  libsystem_c.dylib              0x189457ff0 __cxa_finalize_ranges + 392
    10 libsystem_c.dylib              0x189401390 exit + 24
    11 UIKit                          0x1904567fc +[_UIAlertManager hideAlertsForTermination] + 490
    12 UIKit                          0x1906587cc __102-[UIApplication _handleApplicationDeactivationWithScene:shouldForceExit:transitionContext:completion:]_block_invoke.2100 + 792
    13 UIKit                          0x19065bfdc _runAfterCACommitDeferredBlocks + 292
    14 UIKit                          0x19064dd50 _cleanUpAfterCAFlushAndRunDeferredBlocks + 560
    15 UIKit                          0x1903bd0b4 _afterCACommitHandler + 168
    16 CoreFoundation                 0x18a4c20c0 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 32
    17 CoreFoundation                 0x18a4bfcf0 __CFRunLoopDoObservers + 372
    18 CoreFoundation                 0x18a4c0180 __CFRunLoopRun + 1024
    19 CoreFoundation                 0x18a3ee2b8 CFRunLoopRunSpecific + 444
    20 GraphicsServices               0x18bea2198 GSEventRunModal + 180
    21 UIKit                          0x1904357fc -[UIApplication _run] + 684
    22 UIKit                          0x190430534 UIApplicationMain + 208
    23 GallopTravel                   0x1000d728c main (main.m:14)
    24 libdispatch.dylib              0x1893d15b8 (Missing)
    Code:
    #0. Crashed: com.apple.main-thread
    0  libsystem_kernel.dylib         0x183c4011c __pthread_kill + 8
    1  libsystem_pthread.dylib        0x183d0cef8 pthread_kill + 112
    2  libsystem_c.dylib              0x183bb1dc8 abort + 140
    3  libsystem_malloc.dylib         0x183c6c374 szone_size + 522
    4  libc++.1.dylib                 0x1836ca6a8 std::__1::__shared_weak_count::__release_shared() + 60
    5  SKMaps                         0x100a79370 std::__1::shared_ptr::~shared_ptr() + 28
    6  libsystem_c.dylib              0x183bb2a14 __cxa_finalize_ranges + 428
    7  libsystem_c.dylib              0x183b5d364 exit + 24
    8  UIKit                          0x189299338 +[_UIAlertManager hideAlertsForTermination] + 526
    9  UIKit                          0x1894b7ff8 __102-[UIApplication _handleApplicationDeactivationWithScene:shouldForceExit:transitionContext:completion:]_block_invoke2017 + 796
    10 UIKit                          0x1894bb0c8 _runAfterCACommitDeferredBlocks + 292
    11 UIKit                          0x1894c8a80 _cleanUpAfterCAFlushAndRunDeferredBlocks + 92
    12 UIKit                          0x1891fa5a4 _afterCACommitHandler + 96
    13 CoreFoundation                 0x18405c728 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 32
    14 CoreFoundation                 0x18405a4cc __CFRunLoopDoObservers + 372
    15 CoreFoundation                 0x18405a8fc __CFRunLoopRun + 928
    16 CoreFoundation                 0x183f84c50 CFRunLoopRunSpecific + 384
    17 GraphicsServices               0x18586c088 GSEventRunModal + 180
    18 UIKit                          0x189272088 UIApplicationMain + 204
    19 GallopTravel                   0x100136f7c main (main.m:14)
    20 libdispatch.dylib              0x183b228b8 (Missing)

  4. #4
    Erfahrener skobbler
    Join Date
    11.02.2015
    Posts
    123
    Thank god I'm not the only one. I've been breaking my head around this. Also on 3.0.2 (with the zoom hot fix). My app was stable when it was on 2.5.1.

    For my app they seem to happen while the user is navigating, free drive or a route navigation makes no difference.

    I've not been able to reproduce this in the simulator, but on my device (when on the road) I was. It happens anywhere between 5 minutes to 30 minutes after navigation start. So far have not been able to determine any common denominator, although 2 of my users seem to think it's related to changing connectivity conditions (when riding in bad coverage areas).

    Also noticed that 95% of my crash reports (and also the ones above) have CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_F UNCTION. This, combined with the bad coverage areas, could perhaps??? mean that SKMaps has an observer, listening for network changes, which is deallocated without removing the observer first? Don't know, just guessing, perhaps useful info for the dev team.

    Any news, hot fix or workaround would be highly appreciated. Getting a lot of (not so nice) user feedback on these crashes and even some bad app reviews.
    Last edited by guidove; 04.01.2017 at 21:50.

  5. #5
    Neuer skobbler
    Join Date
    09.01.2017
    Posts
    1
    I have the exact same crash, that occurs when exiting the App.
    My Crashlytics has tons of this crashes.
    Is there any update? Maybe some workaround?

  6. #6
    Erfahrener skobbler
    Join Date
    12.09.2016
    Posts
    112
    At the moment this issue is still under investigation by our Core department.
    The fix will be available with our next SDK release.

  7. #7
    Neuer skobbler
    Join Date
    20.07.2016
    Posts
    6
    We saw the same crashes, and for your interests, please find our crash log below:

    Code:
    0  libsystem_platform.dylib       0x18131d7d0 _os_lock_corruption_abort + 162
    1  libsystem_platform.dylib       0x18131d7d0 _os_lock_corruption_abort + 162
    2  libsystem_pthread.dylib        0x181321c40 pthread_mutex_destroy + 32
    3  SKMaps                         0x100885814 std::__1::__shared_ptr_pointer < TxgPackageInfoWrapper*, std::__1::default_delete < TxgPackageInfoWrapper>, std::__1::allocator < TxgPackageInfoWrapper> >::__on_zero_shared() + 164
    4  libsystem_platform.dylib       0x18131d7d0 _os_lock_corruption_abort + 162
    5  libc++.1.dylib                 0x180ce26a8 std::__1::__shared_weak_count::__release_shared() + 60
    6  SKMaps                         0x100885370 std::__1::shared_ptr::~shared_ptr() + 28
    7  libsystem_c.dylib              0x1811caa14 __cxa_finalize_ranges + 428
    8  libsystem_c.dylib              0x181175364 exit + 24
    Last edited by rshyfn; 12.01.2017 at 01:43.

  8. #8
    Erfahrener skobbler
    Join Date
    11.02.2015
    Posts
    123
    Hi Adrian,

    Thanks for the information. Is there any additional information you can give us as to what situation/scenario causes the crashes and/or a possible workaround? It's not that bad if the crash happens on App exit, but for my app it happens in the middle of navigating --> a lot of unhappy users --> I need to fix this ASAP. If you could give me some more info I might be able to avoid this situation/scenario all together in my app.

    I'm guessing the new SDK release will take a few months more and I really don't like to have an unstable app in the app store all that time.

    Thanks for your answer,
    Guido

  9. #9
    Erfahrener skobbler
    Join Date
    12.09.2016
    Posts
    112
    Hi guidove,
    We are aware of this problems. So far we don't have a planned date, but I'm sure it will be sooner than usual either's gonna be a new release or a hotfix.
    I'll keep you posted.

  10. #10
    Erfahrener skobbler
    Join Date
    11.02.2015
    Posts
    123
    Thanks Adrian. Looking forward to the fix. Best regards

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •