Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-18249] 64bit iOS devices: Intermittent crashes with SDK 3.5.0

GitHub Issuen/a
TypeBug
PriorityHigh
StatusClosed
ResolutionFixed
Resolution Date2015-01-12T09:57:03.000+0000
Affected Version/sRelease 3.5.0
Fix Version/sRelease 3.5.0, Release 4.0.0
ComponentsiOS
Labelsqe-3.5.0
ReporterEric Merriman
AssigneeVishal Duggal
Created2014-12-17T22:58:25.000+0000
Updated2015-01-12T22:58:20.000+0000

Description

Description:

TIMOB-18214 was reported and contains two distinct issues. This ticket is being created to track one of those items. A complex app running on arm64 devices (may also occur on arm7 but we have not witnessed this to date)

Steps to reproduce:

1) Use code sample available internally 2) Install on iPhone 6+, 6 or iPhone 5s 3) Use application features until crash occurs

Result:

Crash

Expected Result:

No crash

Notes

This does not occur with iOS 7.0.3, 7.1.1, or 7.1.2 *THIS IS A REGRESSION* DOES NOT OCCUR in SDK 3.4.1.GA

Comments

  1. Travis Crist 2015-01-05

    This issue is *NOT* present in the following TiSDKs: * 3.1.3.GA * 3.2.1.GA * 3.3.0.GA * 3.4.0.GA * 3.4.1.GA It is only present in the following TiSDKs: * 3.5.0.Alpha * 3.5.0.Beta * 3.5.0.RC
  2. Eric Merriman 2015-01-08

    I am going to reformat the text of this ticket to reflect the crashing behavior. Things are getting a little confused by the data I provided in the original report conflicting with the comments and edits. For example, the logging behavior is not a regression, but it seems the crash is. I will create a new ticket for the logging issue as I have no iron-clad indication the two are related (log output and crash). I will try to provide the most accurate detail on the affected iOS and device information.
  3. Vishal Duggal 2015-01-10

    Pull pending for tijscore https://github.com/appcelerator/tijscore/pull/26 Titanium SDK PR's https://github.com/appcelerator/titanium_mobile/pull/6560 https://github.com/appcelerator/titanium_mobile/pull/6561
  4. Eric Merriman 2015-01-12

    We are confident that the root cause of this issue has been addressed with SDK 3.5.0.v20150112015717.

JSON Source