[TIMOB-8429] iOS: KitchenSink: crash after one hour with endpointIOTimerExpired logs

GitHub Issue	n/a
Type	Bug
Priority	Medium
Status	Closed
Resolution	Invalid
Resolution Date	2012-03-30T09:23:16.000+0000
Affected Version/s	Release 2.0.0
Fix Version/s	n/a
Components	iOS
Labels	qe-ios031912
Reporter	Dustin Hyde
Assignee	Neeraj Gupta
Created	2012-03-29T16:08:13.000+0000
Updated	2013-05-01T20:11:53.000+0000

Description

After using Kitchen Sink for an hour, app crashed with console logs (no crash report). Occurred using UI > Views > Table Views > Events, unable to reproduce. Steps to Reproduce: 1. Run Kitchen Sink for an hour. Expected Result: No crash. Actual Result: Crash.

Attachments

File	Date	Size
kitchensink tableviews events crash.txt	2012-03-29T16:08:13.000+0000	59085

Comments

Stephen Tramer 2012-03-30

This appears to be a testing failure. Based on the log output, what may have happened is that a second instance of Kitchen Sink was launched while one was already operational (check the logs; there's a Kitchen Sink "startup" message after a bunch of layout warning output): bq. Mar 29 16:56:06 unknown UIKitApplication:com.appcelerator.titanium[0xaeb8][11556] : [DEBUG] application booted in 1346.867025 ms In this case it may be that any connection that the first instance had to running services was terminated. We need more information before this bug can be closed as INVALID.
Stephen Tramer 2012-03-30

After talking with Dustin it looks like there may have been some kind of resource contention, and it's possible that the device itself has an issue; check the goog results for "endpointIOTimerExpired" (always seems to involve endpoint 81, as well). Going to mark the bug INVALID as a result and assume it's an apple firmware issue. If the issue can ever be reproduced, please reopen with some detailed information about what was occurring at the time of the crash.
Dustin Hyde 2013-05-01

Closing. This did appear to be a firmware issue.

JSON Source