{ "id": "160905", "key": "TIMOB-23671", "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": "18164", "name": "ioslib 0.12.0", "archived": false, "released": true, "releaseDate": "2016-06-23" }, { "id": "18218", "name": "node-ios-device 0.10.0", "archived": false, "released": true, "releaseDate": "2016-07-26" }, { "id": "18226", "name": "node-ios-device 0.10.1", "archived": false, "released": true, "releaseDate": "2016-07-28" }, { "id": "18237", "name": "node-ios-device 0.11.0", "archived": false, "released": true, "releaseDate": "2016-08-04" }, { "id": "18239", "name": "ioslib 0.13.0", "archived": false, "released": true, "releaseDate": "2016-08-04" }, { "id": "18253", "name": "Release 5.5.0", "archived": false, "released": true, "releaseDate": "2016-09-13" }, { "id": "18274", "name": "node-ios-device 0.11.1", "archived": false, "released": true, "releaseDate": "2016-08-18" }, { "id": "18286", "name": "node-ios-device 0.11.2", "archived": false, "released": true, "releaseDate": "2016-08-24" }, { "id": "18372", "name": "node-ios-device 1.0.0", "archived": false, "released": true, "releaseDate": "2016-10-10" } ], "resolution": { "id": "1", "description": "A fix for this issue is checked into the tree and tested.", "name": "Fixed" }, "resolutiondate": "2016-08-04T16:36:26.000+0000", "created": "2016-06-07T20:15:54.000+0000", "priority": { "name": "Critical", "id": "1" }, "labels": [], "versions": [], "issuelinks": [], "assignee": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "updated": "2018-08-06T17:49:29.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" }, { "id": "10207", "name": "Tooling" } ], "attachment": [ { "id": "59564", "filename": "ac3802.mp4", "author": { "name": "dpfeiffer", "key": "dpfeiffer", "displayName": "Daniel Pfeiffer", "active": true, "timeZone": "America/Chicago" }, "created": "2016-06-10T17:42:30.000+0000", "size": 8726725, "mimeType": "video/mp4" } ], "flagged": false, "summary": "Receiving \"Segmentation fault: 11\" when trying to build after updating SDK to 5.4.0 from June 6 (or later)", "creator": { "name": "dpfeiffer", "key": "dpfeiffer", "displayName": "Daniel Pfeiffer", "active": true, "timeZone": "America/Chicago" }, "subtasks": [], "reporter": { "name": "dpfeiffer", "key": "dpfeiffer", "displayName": "Daniel Pfeiffer", "active": true, "timeZone": "America/Chicago" }, "environment": "Mac OSX 10.11.5\r\nNode 4.4.5\r\nTitanium CLI 5.0.8", "closedSprints": [ { "id": 686, "state": "closed", "name": "2016 Sprint 16 Tooling", "startDate": "2016-07-30T00:42:21.509Z", "endDate": "2016-08-13T00:42:00.000Z", "completeDate": "2016-08-15T08:01:39.795Z", "originBoardId": 199 } ], "comment": { "comments": [ { "id": "387785", "author": { "name": "dpfeiffer", "key": "dpfeiffer", "displayName": "Daniel Pfeiffer", "active": true, "timeZone": "America/Chicago" }, "body": "It seems like if I restart my computer, it will work once. Then seg fault each time after that.", "updateAuthor": { "name": "dpfeiffer", "key": "dpfeiffer", "displayName": "Daniel Pfeiffer", "active": true, "timeZone": "America/Chicago" }, "created": "2016-06-07T20:17:01.000+0000", "updated": "2016-06-07T20:17:01.000+0000" }, { "id": "387786", "author": { "name": "dpfeiffer", "key": "dpfeiffer", "displayName": "Daniel Pfeiffer", "active": true, "timeZone": "America/Chicago" }, "body": "I have tried uninstalling the Titanium CLI and removing the SDK, then reinstalling both, but the issue persists.", "updateAuthor": { "name": "dpfeiffer", "key": "dpfeiffer", "displayName": "Daniel Pfeiffer", "active": true, "timeZone": "America/Chicago" }, "created": "2016-06-07T20:18:14.000+0000", "updated": "2016-06-07T20:18:14.000+0000" }, { "id": "387792", "author": { "name": "dpfeiffer", "key": "dpfeiffer", "displayName": "Daniel Pfeiffer", "active": true, "timeZone": "America/Chicago" }, "body": "Didn't realize there was a problem template. Updating description.", "updateAuthor": { "name": "dpfeiffer", "key": "dpfeiffer", "displayName": "Daniel Pfeiffer", "active": true, "timeZone": "America/Chicago" }, "created": "2016-06-07T21:56:30.000+0000", "updated": "2016-06-07T21:56:30.000+0000" }, { "id": "387935", "author": { "name": "nsalahin", "key": "nsalahin", "displayName": "Nazmus Salahin", "active": true, "timeZone": "Asia/Dhaka" }, "body": "Hello,\r\nThings working as expected in my environment for SDK {{6.0.0.v20160608170004}}. I have tried following commands.\r\n{code}\r\nappc ti sdk install --branch master 6.0.0.v20160608170004\r\nappc ti sdk select 6.0.0.v20160608170004\r\nappc ti build\r\n{code}\r\n*CLI OUTPUT:*\r\n{code}\r\n$ appc ti sdk select 6.0.0.v20160607075329\r\nAppcelerator Command-Line Interface, version 5.2.2\r\nCopyright (c) 2014-2016, Appcelerator, Inc. All Rights Reserved.\r\n\r\n[ERROR] Invalid Titanium SDK \"6.0.0.v20160607075329\"\r\n\r\nInstalled SDKs:\r\n 1) 6.0.0.v20160608170004 [selected] C:\\ProgramData\\Titanium\\mobilesdk\\win32\\6.0.0.v20160608170004\r\n 2) 5.4.0.v20160509133737 C:\\ProgramData\\Titanium\\mobilesdk\\win32\\5.4.0.v20160509133737\r\n 3) 5.4.0.v20160429102159 C:\\ProgramData\\Titanium\\mobilesdk\\win32\\5.4.0.v20160429102159\r\n 4) 5.4.0.v20160405161149 C:\\ProgramData\\Titanium\\mobilesdk\\win32\\5.4.0.v20160405161149\r\n 5) 5.3.0.v20160404105211 C:\\ProgramData\\Titanium\\mobilesdk\\win32\\5.3.0.v20160404105211\r\n 6) 5.3.0.GA C:\\ProgramData\\Titanium\\mobilesdk\\win32\\5.3.0.GA\r\n 7) 5.2.2.GA C:\\ProgramData\\Titanium\\mobilesdk\\win32\\5.2.2.GA\r\n 8) 5.2.1.GA C:\\ProgramData\\Titanium\\mobilesdk\\win32\\5.2.1.GA\r\n 9) 5.2.0.GA C:\\ProgramData\\Titanium\\mobilesdk\\win32\\5.2.0.GA\r\n 10) 5.1.2.GA C:\\ProgramData\\Titanium\\mobilesdk\\win32\\5.1.2.GA\r\n 11) 4.0.0.GA C:\\ProgramData\\Titanium\\mobilesdk\\win32\\4.0.0.GA\r\nTitanium SDK version to select [6.0.0.v20160608170004]:\r\n\r\nConfiguration saved\r\n\r\n\r\nTitanium@GSL /e/AppceleretorWorkspace/ac3800\r\n$ appc ti build\r\nAppcelerator Command-Line Interface, version 5.2.2\r\nCopyright (c) 2014-2016, Appcelerator, Inc. All Rights Reserved.\r\n\r\nTarget platform to build for:\r\n 1) android\r\n 2) mobileweb\r\n 3) windows\r\nEnter # or platform name: 1\r\n\r\n6/9/2016, 3:25:19 PM\r\n\r\nOperating System\r\n Name = Microsoft Windows 8.1 Enterprise N\r\n Version = 6.3.9600\r\n Architecture = 32bit\r\n # CPUs = 4\r\n Memory = 6311747584\r\n\r\nNode.js\r\n Node.js Version = 0.12.7\r\n npm Version = 2.11.3\r\n\r\nTitanium CLI\r\n CLI Version = 5.0.6\r\n\r\nTitanium SDK\r\n SDK Version = 6.0.0.v20160608170004\r\n SDK Path = C:\\ProgramData\\Titanium\\mobilesdk\\win32\\6.0.0.v20160608170004\r\n Target Platform = android\r\n{code}\r\n\r\n*Environment*:\r\n\r\n*Device info:* Nexus7 (android 6.0.1)\r\n*Node.js Version:* 0.12.7\r\n*npm Version:* 2.11.3\r\n*Titanium SDKs:* 6.0.0.v20160608170004\r\n*Java Development Kit Version:* 1.8.0_73\r\n*Titanium CLI Version:* 5.0.6\r\n*Appcelerator CLI Version:* 5.2.2\r\n*Appcelerator Studio:* 4.5.0", "updateAuthor": { "name": "nsalahin", "key": "nsalahin", "displayName": "Nazmus Salahin", "active": true, "timeZone": "Asia/Dhaka" }, "created": "2016-06-09T09:36:25.000+0000", "updated": "2016-06-09T09:36:25.000+0000" }, { "id": "388068", "author": { "name": "dpfeiffer", "key": "dpfeiffer", "displayName": "Daniel Pfeiffer", "active": true, "timeZone": "America/Chicago" }, "body": "Thanks, Nazmus. Unfortunately, I'm still experiencing issues.\r\n\r\nI'm attaching a short screen capture.\r\n\r\nUsing the SDK you mention, I get segmentation fault errors when trying to do _anything_ with ti build. Even just pull up the help documentation.\r\n\r\nHowever, if I switch to an older SDK version, it seems to be okay (it still doesn't build because it forks the new SDK, but I can run the help command).\r\n[^ac3802.mp4]", "updateAuthor": { "name": "dpfeiffer", "key": "dpfeiffer", "displayName": "Daniel Pfeiffer", "active": true, "timeZone": "America/Chicago" }, "created": "2016-06-10T17:43:04.000+0000", "updated": "2016-06-10T17:43:04.000+0000" }, { "id": "388072", "author": { "name": "dpfeiffer", "key": "dpfeiffer", "displayName": "Daniel Pfeiffer", "active": true, "timeZone": "America/Chicago" }, "body": "FWIW, I have Titanium on multiple machines, and they all behave a bit differently:\r\nOn my main machine, it segfaults almost always. If I reboot, sometimes it will work once.\r\nOn my build machine, it seems to work just fine.\r\nOn a coworker's machine, it seems to be 50/50. Sometimes it segfaults, sometimes it doesn't. If he cleans a number of times, then it usually works.\r\n\r\nAnd this all started within the past few days. Before June 6, everything worked fine. As far as I know, we all have the same development environment and it hasn't changed in the past week.", "updateAuthor": { "name": "dpfeiffer", "key": "dpfeiffer", "displayName": "Daniel Pfeiffer", "active": true, "timeZone": "America/Chicago" }, "created": "2016-06-10T17:48:25.000+0000", "updated": "2016-06-10T17:48:25.000+0000" }, { "id": "388089", "author": { "name": "sdarda", "key": "sdarda", "displayName": "Sharif AbuDarda", "active": false, "timeZone": "Asia/Dhaka" }, "body": "Hello, Does this only happens to master releases or for GA releases too?", "updateAuthor": { "name": "sdarda", "key": "sdarda", "displayName": "Sharif AbuDarda", "active": false, "timeZone": "Asia/Dhaka" }, "created": "2016-06-10T20:10:27.000+0000", "updated": "2016-06-10T20:10:27.000+0000" }, { "id": "388090", "author": { "name": "dpfeiffer", "key": "dpfeiffer", "displayName": "Daniel Pfeiffer", "active": true, "timeZone": "America/Chicago" }, "body": "I don't think I have access to GA releases (I'm using the builds from http://builds.appcelerator.com/).\r\nSo--I've only tried on master releases (and more recent releases from 5.4.x branch).", "updateAuthor": { "name": "dpfeiffer", "key": "dpfeiffer", "displayName": "Daniel Pfeiffer", "active": true, "timeZone": "America/Chicago" }, "created": "2016-06-10T20:21:53.000+0000", "updated": "2016-06-10T20:21:53.000+0000" }, { "id": "388130", "author": { "name": "nsalahin", "key": "nsalahin", "displayName": "Nazmus Salahin", "active": true, "timeZone": "Asia/Dhaka" }, "body": "Hello [~dpfeiffer],\r\nTry installing latest GA release with following command and then try building apps with this SDK.\r\n{code}\r\nappc ti sdk install 5.3.0.GA\r\n{code}\r\nAlso please give us your environment details. You can get that with following command.\r\n{code}\r\nappc info\r\n{code}\r\n\r\nThanks in advance", "updateAuthor": { "name": "nsalahin", "key": "nsalahin", "displayName": "Nazmus Salahin", "active": true, "timeZone": "Asia/Dhaka" }, "created": "2016-06-12T05:14:06.000+0000", "updated": "2016-06-12T05:14:06.000+0000" }, { "id": "390820", "author": { "name": "wluu", "key": "wluu", "displayName": "Wilson Luu", "active": false, "timeZone": "America/Los_Angeles" }, "body": "So far, we are unable to reproduce this issue internally. We tried the following:\r\n\r\n* Switch node version using the n node module; 0.12.5, 4.4.5, 4.4.7\r\n* Used both Titanium CLI (5.0.8, 5.0.9) and Appc CLI (5.3.1, 5.4.0-31, 5.4.0-33) to create and build a mobile project (appc new, appc run, ti create, ti build, appc ti build)\r\n* Used Titanium SDK 5.3.1.GA, 5.4.0.v20160713141635, 6.0.0.v20160607075329\r\n* And used Xcode 7.3.1\r\n\r\nBelow are the listed steps we tried:\r\n\r\n*Possible steps with Appc CLI only:*\r\n# Download and install n node module\r\n# Use n to switch node 0.12.5 from node 4.4.7: {{sudo n 0.12.5}}\r\n# Install Titanium SDK 5.3.1.GA: {{appc ti sdk install 5.3.1.GA}}\r\n*Note:* A message will appear saying it will recompile the Appc CLI Core if you installed Appc CLI Core with Node greater than 0.12.X.\r\n# Created a mobile project with: {{appc new}}\r\n# Run the project with: {{appc run -p ios}}; no issue\r\n# Using n node module, switch to node 4.4.7: {{sudo n 4.4.7}}\r\n# Clean same mobile project: {{appc ti clean}}\r\n*Note:* A message will appear saying it will recompile the Appc CLI Core.\r\n# Install and select latest 5.4.0 SDK\r\n# Changed SDK in tiapp.xml to selected version\r\n# Run and build again: {{appc run -p ios}}; no issue\r\n\r\n*Possible steps with Titanium CLI only:*\r\n# Download and install n node module\r\n# Use n to switch node 0.12.5 from node 4.4.7: {{sudo n 0.12.5}}\r\n# Install Titanium SDK 5.3.1.GA: {{ti sdk install 5.3.1.GA}}\r\n# Created a mobile project with: {{ti create}}\r\n# Run the project with: {{ti build -p ios}}; no issue\r\n# Using n node module, switch to node 4.4.7: {{sudo n 4.4.7}}\r\n# Clean same mobile project: {{ti clean}}\r\n# Install and select latest 5.4.0 SDK\r\n# Changed SDK in tiapp.xml to selected version\r\n# Run and build again: {{ti build -p ios}}; no issue\r\n\r\n", "updateAuthor": { "name": "wluu", "key": "wluu", "displayName": "Wilson Luu", "active": false, "timeZone": "America/Los_Angeles" }, "created": "2016-07-15T21:02:32.000+0000", "updated": "2016-07-15T21:02:32.000+0000" }, { "id": "390905", "author": { "name": "dpfeiffer", "key": "dpfeiffer", "displayName": "Daniel Pfeiffer", "active": true, "timeZone": "America/Chicago" }, "body": "Thanks, Wilson.\r\n\r\nWe rolled back to the 5.3.1GA and haven't been having these issues.\r\nHowever, when we tried to preview the latest continuous integration builds (like the ones mentioned in the description), the seg faults are introduced.", "updateAuthor": { "name": "dpfeiffer", "key": "dpfeiffer", "displayName": "Daniel Pfeiffer", "active": true, "timeZone": "America/Chicago" }, "created": "2016-07-18T13:49:23.000+0000", "updated": "2016-07-18T13:49:23.000+0000" }, { "id": "390941", "author": { "name": "wluu", "key": "wluu", "displayName": "Wilson Luu", "active": false, "timeZone": "America/Los_Angeles" }, "body": "[~dpfeiffer], Couple of things:\r\n\r\n# Which Xcode version you are using?\r\n# Which Android SDK, Platform, and Build tools are you using? Android NDK?\r\n# Can you try using https://www.npmjs.com/package/segfault-handler to capture more detailed information on the seg fault?\r\n## In terminal, go to the location of your *selected* SDK e.g. {{cd ~/Library/Application Support/Titanium/mobilesdk/osx/6.0.0.v20160718080315}}\r\n## Install segfault-handler node module: {{npm install segfault-handler}}\r\n## Next, open the {{build.js}} file; go to: {{/cli/commands/build.js}}\r\n## Include the following lines of code at the top of the {{build.js}} file:\r\n{code}\r\nvar SegfaultHandler = require('segfault-handler');\r\nSegfaultHandler.registerHandler('crash.log');\r\n{code}\r\n## Save your changes and reproduce your issue; the {{crash.log}} file will be generated where ever you run the build command", "updateAuthor": { "name": "wluu", "key": "wluu", "displayName": "Wilson Luu", "active": false, "timeZone": "America/Los_Angeles" }, "created": "2016-07-18T20:49:28.000+0000", "updated": "2016-07-18T20:49:28.000+0000" }, { "id": "391074", "author": { "name": "rdperottoni", "key": "rdperottoni", "displayName": "Rodolfo Perottoni", "active": true, "timeZone": "Australia/Brisbane" }, "body": "Can someone open this ticket again? I've just got this error showing up for me and don't know what else to do. \r\nI've tried:\r\n\r\n- Uninstalling APPC CLI / Titanium CLI and installing again\r\n- Using multiple versions of Ti SDK / APPC CLI / Titanium CLI\r\n- Trying to build all of my previous projects (many different versions of SDK): none works\r\n- Building via Studio / Command line - none works\r\n\r\nThis problem started since 5.4.0.v20160617074028.\r\nPreviously i was having to run \"ti build \" a few times and after a while it would start working again, but today (20/Jul) it stopped for real.\r\n\r\nI ran out of options here guys. Should i reset my Mac to factory defaults now ? ", "updateAuthor": { "name": "rdperottoni", "key": "rdperottoni", "displayName": "Rodolfo Perottoni", "active": true, "timeZone": "Australia/Brisbane" }, "created": "2016-07-20T05:47:24.000+0000", "updated": "2016-08-01T23:10:49.000+0000" }, { "id": "391077", "author": { "name": "rdperottoni", "key": "rdperottoni", "displayName": "Rodolfo Perottoni", "active": true, "timeZone": "Australia/Brisbane" }, "body": "I'm starting to think this is not a local problem. Reasons?\r\n\r\n-> It started after i logged in with a Pro account and tried to build a hyperloop-enabled project\r\n-> I've uninstalled APPC CLI, Titanium CLI, NodeJS, all SDKs. Then i've also deleted all hidden folders on my local User folder (*.appcelerator*, *.titanium*)\r\n-> I've reinstalled everything from scratch. I still can't run any projects with that account.\r\n-> My colleague tried logging into the same account on another computer. He can't build any projects with it as well.\r\n\r\nIt's very unlikely that you guys will be able to replicate this issue easily. If you still can't, i can provide the example project and the details of my account so you can log into it and look at that error.\r\nThanks guys.\r\n", "updateAuthor": { "name": "rdperottoni", "key": "rdperottoni", "displayName": "Rodolfo Perottoni", "active": true, "timeZone": "Australia/Brisbane" }, "created": "2016-07-20T07:55:48.000+0000", "updated": "2016-07-20T07:55:48.000+0000" }, { "id": "391078", "author": { "name": "rdperottoni", "key": "rdperottoni", "displayName": "Rodolfo Perottoni", "active": true, "timeZone": "Australia/Brisbane" }, "body": "Just tried using 5.3.1.GA with a project that *does not have hyperloop*. Works like a charm. If i change it to run with 5.4.0+, it stops working.\r\n", "updateAuthor": { "name": "rdperottoni", "key": "rdperottoni", "displayName": "Rodolfo Perottoni", "active": true, "timeZone": "Australia/Brisbane" }, "created": "2016-07-20T08:19:40.000+0000", "updated": "2016-07-20T08:19:40.000+0000" }, { "id": "391080", "author": { "name": "xicovarisco_orange", "key": "xicovarisco_orange", "displayName": "Francisco Ruaro Varisco", "active": true, "timeZone": "America/Los_Angeles" }, "body": "The only 5.4.X SDK version that runs some Hyperloop project is the v20160413200113.\r\nStill not the best scenario as this versions has a bunch of bugs. \r\n\r\nI'm suspecting the issue is something related to the accounts check (If you have a PRO account or not)", "updateAuthor": { "name": "xicovarisco_orange", "key": "xicovarisco_orange", "displayName": "Francisco Ruaro Varisco", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2016-07-20T08:39:54.000+0000", "updated": "2016-07-20T08:39:54.000+0000" }, { "id": "391095", "author": { "name": "wluu", "key": "wluu", "displayName": "Wilson Luu", "active": false, "timeZone": "America/Los_Angeles" }, "body": "[~rdperottoni], [~xicovarisco_orange], Can you try adding the segfault-handler node module (see my last comment) and see if you can capture more detailed information about the segfault?\r\n\r\n[~rdperottoni], Yes, please attach your project that is showing this issue.", "updateAuthor": { "name": "wluu", "key": "wluu", "displayName": "Wilson Luu", "active": false, "timeZone": "America/Los_Angeles" }, "created": "2016-07-20T16:54:34.000+0000", "updated": "2016-07-20T17:04:51.000+0000" }, { "id": "391122", "author": { "name": "dpfeiffer", "key": "dpfeiffer", "displayName": "Daniel Pfeiffer", "active": true, "timeZone": "America/Chicago" }, "body": "1. Xcode 7.3.1.\r\n2. Android SDK 23; build tools 23; NDK r10d\r\n3. The entirety of the crash.log is below:\r\n\r\n\r\n{noformat}\r\nPID 8549 received SIGSEGV for address: 0x0\r\n0 segfault-handler.node 0x00000001016f0fe8 _ZL16segfault_handleriP9__siginfoPv + 280\r\n1 libsystem_platform.dylib 0x00007fff83ac252a _sigtramp + 26\r\n2 ??? 0x00000000000007a1 0x0 + 1953\r\n3 node_ios_device.node 0x000000010438e441 _ZL13getDeviceInfoP6Device + 357\r\n4 node_ios_device.node 0x0000000104397daf _ZNSt3__114__thread_proxyINS_5tupleIJPFvP6DeviceES3_EEEEEPvS7_ + 62\r\n5 libsystem_pthread.dylib 0x00007fff87e6299d _pthread_body + 131\r\n6 libsystem_pthread.dylib 0x00007fff87e6291a _pthread_body + 0\r\n7 libsystem_pthread.dylib 0x00007fff87e60351 thread_start + 13\r\n{noformat}\r\n\r\n\r\nThis is the same log regardless of whether I build for Android or iOS.", "updateAuthor": { "name": "dpfeiffer", "key": "dpfeiffer", "displayName": "Daniel Pfeiffer", "active": true, "timeZone": "America/Chicago" }, "created": "2016-07-20T19:58:41.000+0000", "updated": "2016-07-20T20:00:53.000+0000" }, { "id": "391133", "author": { "name": "wluu", "key": "wluu", "displayName": "Wilson Luu", "active": false, "timeZone": "America/Los_Angeles" }, "body": "[~dpfeiffer], Still can't reproduce the issue with your Xcode and Android stack. *But,* the seg fault log that you provided seems interesting. The log indicates that the iOS issue may lie within the {{node-ios-device}} node module. For Android, not too sure still.\r\n\r\nTo confirm the iOS issue:\r\n# Go to your 5.3.1.GA SDK and copy {{ioslib}} node module e.g.: {{~/Library/Application Support/Titanium/mobilesdk/osx/5.3.1.GA/node_modules}}\r\n# In your selected SDK that's generating the seg fault, *attach* the {{ioslib}} node module to this ticket, then delete and replace it with the one from 5.3.1.GA SDK. e.g. {{~/Library/Application Support/Titanium/mobilesdk/osx//node_modules}}\r\n# Next, edit the {{package.json}} to contain the correct {{ioslib}} version e.g. : {{~/Library/Application Support/Titanium/mobilesdk/osx//package.json}}. The {{ioslib}} version from 5.3.1.GA SDK should be 0.10.4\r\n# Try to reproduce", "updateAuthor": { "name": "wluu", "key": "wluu", "displayName": "Wilson Luu", "active": false, "timeZone": "America/Los_Angeles" }, "created": "2016-07-20T21:44:42.000+0000", "updated": "2016-07-20T21:44:42.000+0000" }, { "id": "391166", "author": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "body": "This error has nothing to do with Android, so we can ignore it.\r\n\r\nIt's nice to have captured the segfault info. It only verifies that node-ios-device is the culprit. node-ios-device is the only native code that Node calls in the entire Titanium CLI or Titanium build.\r\n\r\nThe version of node-ios-device in 5_4_X and master branches is v0.9.5 which had significant internal changes. There were fixes for race conditions, Node 6 support, updated Boost version, and node-pre-gyp. It's likely that a regression has been introduced.\r\n\r\nOK, so looking at the segfault stack, we see that {{node_ios_device.node}} choked on something after {{_ZL13getDeviceInfoP6Device}}. node-ios-device is open source, so you could easily look up that function to see what's going on: https://github.com/appcelerator/node-ios-device/blob/master/src/ios-device.cpp#L198. {{getDeviceInfo()}} is run on a background thread. {{getDeviceInfo()}} has a shared mutex so that we only query a single device at a time. The shared mutex instance is from Boost.\r\n\r\nBoost is mostly headers, but does require two precompiled static libraries: {{libboost_system-mt.a}} and {{libboost_thread-mt.a}}. The precompiled Boost libraries are in the deps folder of node-ios-device: https://github.com/appcelerator/node-ios-device/tree/master/deps/boost/lib. I had issues compiling Boost so I cheated and installed them via MacPorts. I have no idea how exactly those were compiled. It's possible they were compiled against a library or with some configuration that causes the segfault at runtime.\r\n\r\nI propose I update the Boost dependencies by recompiling them, then recompile node-ios-device and publish a v0.9.6. Then update ioslib and Titanium SDK's 5_4_X and master branch with the latest ioslib and node-ios-device. I'm hoping that will fix the problem.", "updateAuthor": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "created": "2016-07-21T03:52:35.000+0000", "updated": "2016-07-21T03:52:35.000+0000" }, { "id": "391202", "author": { "name": "dpfeiffer", "key": "dpfeiffer", "displayName": "Daniel Pfeiffer", "active": true, "timeZone": "America/Chicago" }, "body": "Thanks, Chris. Wilson--do you still need me to try and reproduce by swapping out the {{ioslib}} module? It seems like the source of the issue is pretty clear (although maybe not the cause yet).", "updateAuthor": { "name": "dpfeiffer", "key": "dpfeiffer", "displayName": "Daniel Pfeiffer", "active": true, "timeZone": "America/Chicago" }, "created": "2016-07-21T16:23:09.000+0000", "updated": "2016-07-21T16:23:09.000+0000" }, { "id": "391203", "author": { "name": "wluu", "key": "wluu", "displayName": "Wilson Luu", "active": false, "timeZone": "America/Los_Angeles" }, "body": "[~dpfeiffer], No, I think we're good. Thanks for the assist :)", "updateAuthor": { "name": "wluu", "key": "wluu", "displayName": "Wilson Luu", "active": false, "timeZone": "America/Los_Angeles" }, "created": "2016-07-21T16:33:57.000+0000", "updated": "2016-07-21T16:33:57.000+0000" }, { "id": "391573", "author": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "body": "node-ios-device PR: https://github.com/appcelerator/node-ios-device/pull/17", "updateAuthor": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "created": "2016-07-26T23:10:00.000+0000", "updated": "2016-07-26T23:10:00.000+0000" }, { "id": "391890", "author": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "body": "I've published node-ios-device 0.10.1 which should solve the seg fault and address an issue where node-ios-device would hang due to what I believe is a deadlock. I'll be publishing a new version of ioslib shortly and updating Titanium SDK.", "updateAuthor": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "created": "2016-07-28T21:00:58.000+0000", "updated": "2016-07-28T21:00:58.000+0000" }, { "id": "392160", "author": { "name": "rdperottoni", "key": "rdperottoni", "displayName": "Rodolfo Perottoni", "active": true, "timeZone": "Australia/Brisbane" }, "updateAuthor": { "name": "rdperottoni", "key": "rdperottoni", "displayName": "Rodolfo Perottoni", "active": true, "timeZone": "Australia/Brisbane" }, "created": "2016-08-01T23:00:33.000+0000", "updated": "2016-08-01T23:33:19.000+0000" }, { "id": "392162", "author": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "body": "[~rdperottoni] You can save your time. I have already fixed the seg fault issue.\r\n\r\nUnfortunately, I uncovered 2 other issues related to the run loops and deadlocks. I'm actively working on a fix.", "updateAuthor": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "created": "2016-08-01T23:35:13.000+0000", "updated": "2016-08-01T23:35:13.000+0000" }, { "id": "392163", "author": { "name": "rdperottoni", "key": "rdperottoni", "displayName": "Rodolfo Perottoni", "active": true, "timeZone": "Australia/Brisbane" }, "body": "@Chris Barber i've seen the PR, but i'm just curious to know why node-ios-device is called even when you're trying to build the project for Android platform... any clue ? \r\nOh, and by the way: is there any way we can use that latest node-ios-version you published before a new SDK version ? Thanks.", "updateAuthor": { "name": "rdperottoni", "key": "rdperottoni", "displayName": "Rodolfo Perottoni", "active": true, "timeZone": "Australia/Brisbane" }, "created": "2016-08-01T23:39:24.000+0000", "updated": "2016-08-01T23:40:08.000+0000" }, { "id": "392165", "author": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "body": "[~rdperottoni] Good question! Basically the Titanium CLI doesn't know anything about the \"build\" command. It identifies the command is \"build\", then loads it. Upon loading it, it calls the build command's {{config()}} handler which returns the build command flags, options, subcommands, and platform specific build command config settings. This means each platform has to return its options and subsequent values so the CLI can validate them. In order to get the values, it needs to query the iOS development environment. This makes things nice when doing {{ti build -h}} or when building from the CLI and it prompts you for a missing or invalid option.\r\n\r\nWe are working on overhauling the CLI which would resolve this issue and speed things up drastically, but that's a ways off.\r\n\r\nWe don't support updating node-ios-device in a Titanium SDK. I hesitate to even tell you how to do it being that the latest published node-ios-device is flawed. I ask that you please wait until I'm able to fix it.", "updateAuthor": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "created": "2016-08-01T23:49:14.000+0000", "updated": "2016-08-01T23:49:14.000+0000" }, { "id": "392166", "author": { "name": "rdperottoni", "key": "rdperottoni", "displayName": "Rodolfo Perottoni", "active": true, "timeZone": "Australia/Brisbane" }, "body": "Thanks for the explanation :).\r\nYeah, i've tried installing 0.10.1 through *npm*, but i'm still getting the error. I'll just wait for the fix then. Thanks for the help so far mate.", "updateAuthor": { "name": "rdperottoni", "key": "rdperottoni", "displayName": "Rodolfo Perottoni", "active": true, "timeZone": "Australia/Brisbane" }, "created": "2016-08-01T23:54:04.000+0000", "updated": "2016-08-01T23:54:04.000+0000" }, { "id": "392396", "author": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "body": "I've finished fixing all the bugs and design flaws with node-ios-device. PR: https://github.com/appcelerator/node-ios-device/pull/20\r\n\r\nNeed to do more testing. I published a beta build: {{node-ios-device@0.11.0-beta}}.\r\n\r\nIf it looks good, I'll publish the v0.11.0 and updating ioslib and Titanium SDK.", "updateAuthor": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "created": "2016-08-04T07:27:01.000+0000", "updated": "2016-08-04T07:27:01.000+0000" }, { "id": "392427", "author": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "body": "Just did some testing and node-ios-device v0.11.0 works like a champ. Published to v0.11.0 to NPM.\r\n\r\nHere's the PR for ioslib: https://github.com/appcelerator/ioslib/pull/39\r\n\r\nioslib v0.13.0 published.", "updateAuthor": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "created": "2016-08-04T15:40:55.000+0000", "updated": "2016-08-04T15:53:48.000+0000" }, { "id": "392435", "author": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "body": "Here's the PR for Titanium SDK master: https://github.com/appcelerator/titanium_mobile/pull/8191", "updateAuthor": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "created": "2016-08-04T16:33:58.000+0000", "updated": "2016-08-04T16:33:58.000+0000" }, { "id": "393175", "author": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "body": "5_5_X PR https://github.com/appcelerator/titanium_mobile/pull/8229", "updateAuthor": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "created": "2016-08-15T16:26:51.000+0000", "updated": "2016-08-15T16:26:51.000+0000" }, { "id": "393646", "author": { "name": "jlongton", "key": "jlongton", "displayName": "Josh Longton", "active": true, "timeZone": "Europe/London" }, "body": "[~rdperottoni] Would you be able to confirm this fix works for you, I am unable to reproduce the issue in order to verify it. ", "updateAuthor": { "name": "jlongton", "key": "jlongton", "displayName": "Josh Longton", "active": true, "timeZone": "Europe/London" }, "created": "2016-08-19T19:02:30.000+0000", "updated": "2016-08-19T19:02:30.000+0000" }, { "id": "394019", "author": { "name": "rdperottoni", "key": "rdperottoni", "displayName": "Rodolfo Perottoni", "active": true, "timeZone": "Australia/Brisbane" }, "body": "I'll try this afternoon. Please note that this error occurred very sporadically, so i'm not sure if i will be able to give an answer soon.\r\n", "updateAuthor": { "name": "rdperottoni", "key": "rdperottoni", "displayName": "Rodolfo Perottoni", "active": true, "timeZone": "Australia/Brisbane" }, "created": "2016-08-24T00:43:29.000+0000", "updated": "2016-08-24T00:43:29.000+0000" }, { "id": "440191", "author": { "name": "emerriman", "key": "emerriman", "displayName": "Eric Merriman ", "active": true, "timeZone": "America/Los_Angeles" }, "body": "Cleaning up older fixed issues. If this issue should not have been closed as fixed, please reopen.", "updateAuthor": { "name": "emerriman", "key": "emerriman", "displayName": "Eric Merriman ", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2018-08-06T17:49:29.000+0000", "updated": "2018-08-06T17:49:29.000+0000" } ], "maxResults": 37, "total": 37, "startAt": 0 } } }