{ "id": "63290", "key": "TIMOB-2658", "fields": { "issuetype": { "id": "1", "description": "A problem which impairs or prevents the functions of the product.", "name": "Bug", "subtask": false }, "project": { "id": "10153", "key": "TIMOB", "name": "Titanium SDK/CLI", "projectCategory": { "id": "10100", "description": "Titanium and related SDKs used in application development", "name": "Client" } }, "fixVersions": [ { "id": "11235", "name": "Release 1.6.0 M02", "archived": true, "released": true, "releaseDate": "2010-12-27" } ], "resolution": { "id": "1", "description": "A fix for this issue is checked into the tree and tested.", "name": "Fixed" }, "resolutiondate": "2011-04-17T01:59:44.000+0000", "created": "2011-04-15T03:26:09.000+0000", "priority": { "name": "Low", "id": "4" }, "labels": [ "crash", "ios", "release-1.6.0" ], "versions": [], "issuelinks": [], "assignee": { "name": "stephentramer", "key": "stephentramer", "displayName": "Stephen Tramer", "active": true, "timeZone": "America/Los_Angeles" }, "updated": "2011-04-17T01:59:44.000+0000", "status": { "description": "The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.", "name": "Closed", "id": "6", "statusCategory": { "id": 3, "key": "done", "colorName": "green", "name": "Done" } }, "components": [ { "id": "10206", "name": "iOS", "description": "iOS Platform" } ], "description": "{html}
Under certain (very rare) circumstances, apps will crash upon\nresume. This appears to be because in iOS 4.0, an app may still be\nin the \"terminating\" state when it is re-resumed if the system\ndetermined that it should be shut down. If the app is locked and\nwaiting on the main thread for a response, this may cause the OS to\nterminate the app for not responding in time when resuming.
\nThe issue appears to come from -[AnalyticsModule shutdown:],\nwhere an HTTP request is scheduled on the main thread. Marking\nmedium because it's such a weird corner case and hard to\nreproduce.
\nBug may not be reproducible enough to reliably test a fix. This\none is 100% crash log.
I've seen this issue pop up a number of times in my users' crash\nlogs. My app has analytics disabled, so that doesn't seem to be the\nsole cause. At the time it looked like the app was freezing in\nredraw code, so it's possible my users won't see this once I put\nout a new version based on Ti 1.5.
If you would be able to provide crash logs that would be\nextremely helpful. If you can symbolize them first at all, that\nwould be great. The instructions here indicate how to do that:
\nHere's one I have on hand.
And not sure if this is related or a separate issue, but from\nthe same user
These seem to have a different underlying cause, but if these\nissues persist after an upgrade to 1.5.0, please file a ticket for\nthem. There were a large number of changes to the view drawing\nsystem that may have fixed these issues.
yep, thought as much. I'll let you know if they crop up again\nafter I ship with 1.5.
(from [3165d74ad25b899f6d820b2ca76352fe13d9001a])\n[#2658 state:fixed-in-qa] Speed up shutdown\nanalytics events by reducing timeout. \nhttps://github.com/appcelerator/titanium_mobile/commit/3165d74ad25b...
not much I can do about this one, closing
Stephen: I haven't seen log1 pop up again, but I'm still getting\nlog2 on 1.5.1. I created a helpdesk ticket which includes new logs\nwith full symbols, and it appears to be a deadlock in NSCondition:\nhttp://developer.appcelerator.com/helpdesk/view/66761
Damien, we're aware that there are some deadlock problems with\ncertain UI operations right now, and we're trying to track all of\nthem down. If you can create a new bug to track this issue and\ninclude the HD link/crash logs with it I would appreciate it.
Getting identical issues described in this support ticket:
\nhttp://developer.appcelerator.com/helpdesk/view/76350