question

tifr0z asked Jan 29, '16

iOS controller crash

All the info I have is the Crashlytics crash reports - the app is using the latest Fling SDK (v1.2.1) EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0xc000000012e6fbc2 Thread : Crashed: Thread 0 webtv 0x1006eaf14 whisperplay::WhisperPlayCore::dispatch(whisperlink::base::Message*) + 3596 1 webtv 0x1006e9654 whisperplay::WhisperPlayCore::run() + 76 2 webtv 0x1007d06f8 apache::thrift::concurrency::PthreadThread::threadMain(void*) + 316 3 libsystem_pthread.dylib 0x1836fbb28 _pthread_body + 156 4 libsystem_pthread.dylib 0x1836fba8c _pthread_body + 154 5 libsystem_pthread.dylib 0x1836f9028 thread_start + 4

amazon fling

10 |5000

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

tifr0z answered Jan 29, '16

Here is a capture of the logs before the crash: 2016-01-29 13:44:33.819 webtv[1754:670457] 1454103873.819419:whisperplay:wp-api:perf:public:start:WPInitialize: Whisperplay initialize 2016-01-29 13:44:33.819 webtv[1754:670457] 1454103873.819659:whisperplay:wp-api:perf:public:start:WPInitializeCallback: Whisperplay initialize callback Thrift: Fri Jan 29 13:44:33 2016 port number UDP socket is bound to 52608 2016-01-29 13:44:33.967 webtv[1754:670522] ******** InstallWPStateListener.onInitialized called ************** 2016-01-29 13:44:33.968 webtv[1754:670522] ******** handleWPReady ************** 2016-01-29 13:44:34.030 webtv[1754:670457] ******** teardown: unregisterCallback ************** 2016-01-29 13:44:34.031 webtv[1754:670457] ******** unregisterCallback ************** 2016-01-29 13:44:34.069 webtv[1754:670457] ******** suspend WP ************** 2016-01-29 13:44:34.072 webtv[1754:670457] ******** suspend WP **************

10 |5000

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Levon@Amazon answered Feb 1, '16

Hi tifr0z, We have not seen this type of crash in our testing. From the logs, it appears that "suspend" is being called twice in succession. This is unusual. Could you please help us with the following questions: - How often have you noticed this crash? - Can the use case be inferred from the application specific logs? Thanks, Amazon Fling SDK Support Team

10 |5000

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

tifr0z answered Feb 3, '16

Thanks for your answer I was hoping you would have an easy answer based on the provided logs - if not...this is a low priority bug as this point because we can't reproduce the bug at will (and so we are hoping this is a low-frequency crash). I will follow up if needed as we find out more To answer your questions with the info available now: -We've only noticed the crash in a test environment because the app isn't live yet, I don't think the issue was seen more than a few times so far - but we have just begun testing. - I believe the crash occurred when waking up the controller app after sending it in the background.

10 |5000

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Levon@Amazon answered Feb 4, '16

Thank you for the information, We were not able to reproduce the behavior in the limited stress testing round using the Install sample as well as the Fling+Install sample in the SDK. We will keep an eye on this scenario and try to reproduce this crash. Best regards, Amazon Fling SDK Support Team

10 |5000

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.