{
	"id": "117065",
	"key": "TIMOB-14518",
	"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": [],
		"resolution": {
			"id": "3",
			"description": "The problem is a duplicate of an existing issue.",
			"name": "Duplicate"
		},
		"resolutiondate": "2013-07-11T01:05:29.000+0000",
		"created": "2013-07-10T22:09:15.000+0000",
		"priority": {
			"name": "High",
			"id": "2"
		},
		"labels": [],
		"versions": [],
		"issuelinks": [
			{
				"id": "30135",
				"type": {
					"id": "10002",
					"name": "Duplicate",
					"inward": "is duplicated by",
					"outward": "duplicates"
				},
				"outwardIssue": {
					"id": "115405",
					"key": "TISTUD-4848",
					"fields": {
						"summary": "Code Processor: \"RangeError: Maximum call stack size exceeded\" error when enabling all Analyzer options",
						"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"
							}
						},
						"priority": {
							"name": "High",
							"id": "2"
						},
						"issuetype": {
							"id": "1",
							"description": "A problem which impairs or prevents the functions of the product.",
							"name": "Bug",
							"subtask": false
						}
					}
				}
			}
		],
		"assignee": {
			"name": "bhughes",
			"key": "bhughes",
			"displayName": "Bryan Hughes",
			"active": true,
			"timeZone": "America/Los_Angeles"
		},
		"updated": "2014-06-19T12:44:05.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": "13102",
				"name": "Code Processor",
				"description": "Analyzes JavaScript source"
			}
		],
		"description": "DEMANDWARE - Code Analyzer failed on Endless Aisle app - \"node.js maximum call stack size exceeded. Increasing the stack size may allow the project to be fully analyzed\"\r\n\r\nThey just installed Appc Studio today (7/10/13) as part of a Trial of Platform and Code Analyzer is working fine for a hello world app but not for their imported production iPad app.\r\n\r\nWe searched Google but could not see how to increase the stack size.\r\n\r\nI am waiting for diagnostics and log form the client and will attach when received.",
		"attachment": [
			{
				"id": "40663",
				"filename": "diag_and_log_20130711.rtf",
				"author": {
					"name": "lbrenman",
					"key": "lbrenman",
					"displayName": "Leor Brenman",
					"active": true,
					"timeZone": "America/Havana"
				},
				"created": "2013-07-11T13:23:48.000+0000",
				"size": 18330,
				"mimeType": "text/rtf"
			}
		],
		"flagged": false,
		"summary": "DEMANDWARE TRIAL - Code Analyzer failed on Endless Aisle app - \"node.js maximum call stack size exceeded. Increasing the stack size may allow the project to be fully analyzed\"",
		"creator": {
			"name": "lbrenman",
			"key": "lbrenman",
			"displayName": "Leor Brenman",
			"active": true,
			"timeZone": "America/Havana"
		},
		"subtasks": [],
		"reporter": {
			"name": "lbrenman",
			"key": "lbrenman",
			"displayName": "Leor Brenman",
			"active": true,
			"timeZone": "America/Havana"
		},
		"environment": "Demandware's dev environment is mac os and they are building/testing iPad apps only",
		"comment": {
			"comments": [
				{
					"id": "261388",
					"author": {
						"name": "bhughes",
						"key": "bhughes",
						"displayName": "Bryan Hughes",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "Duplicate of TISTUD-4848",
					"updateAuthor": {
						"name": "bhughes",
						"key": "bhughes",
						"displayName": "Bryan Hughes",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2013-07-11T01:05:29.000+0000",
					"updated": "2013-07-11T01:05:29.000+0000"
				},
				{
					"id": "261389",
					"author": {
						"name": "bhughes",
						"key": "bhughes",
						"displayName": "Bryan Hughes",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "FWIW there currently is no way to increase the stack size if you are calling it from Studio. I believe that there are plans to add the ability to increase the stack size from studio sometime in the future (hence why this is a duplicate of a Studio bug).",
					"updateAuthor": {
						"name": "bhughes",
						"key": "bhughes",
						"displayName": "Bryan Hughes",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2013-07-11T01:06:49.000+0000",
					"updated": "2013-07-11T01:06:49.000+0000"
				},
				{
					"id": "261427",
					"author": {
						"name": "lbrenman",
						"key": "lbrenman",
						"displayName": "Leor Brenman",
						"active": true,
						"timeZone": "America/Havana"
					},
					"body": "In TISTUD-4848 Nam suggests the following workaround:\n\nTo work-around this issue:\n\nFind the Code Analyzer preferences under Studio > Code Analyzer\nUncheck the option 'Process Unvisited Code'\nSave the changes\n\nDemandware tried this and it did not work :(",
					"updateAuthor": {
						"name": "lbrenman",
						"key": "lbrenman",
						"displayName": "Leor Brenman",
						"active": true,
						"timeZone": "America/Havana"
					},
					"created": "2013-07-11T13:22:19.000+0000",
					"updated": "2013-07-11T13:22:19.000+0000"
				},
				{
					"id": "261428",
					"author": {
						"name": "lbrenman",
						"key": "lbrenman",
						"displayName": "Leor Brenman",
						"active": true,
						"timeZone": "America/Havana"
					},
					"body": "Studio Diag and Log after attempting the workaround",
					"updateAuthor": {
						"name": "lbrenman",
						"key": "lbrenman",
						"displayName": "Leor Brenman",
						"active": true,
						"timeZone": "America/Havana"
					},
					"created": "2013-07-11T13:23:48.000+0000",
					"updated": "2013-07-11T13:23:48.000+0000"
				},
				{
					"id": "261455",
					"author": {
						"name": "bhughes",
						"key": "bhughes",
						"displayName": "Bryan Hughes",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "You'll have to increase the stack size for node from the command line then, which requires running the code analyzer from the command line. Assuming they are running on OS X or Linux, the command should look something like:\n\n\"node --stack-size=10000 /usr/local/bin/titanium analyze -p <platform, e.g. iphone> -A -R <path/to/results/directory>\"\n\nThis command says to increase the stack size to 10000 (it typically defaults to 1000). Finding the correct size is a bit of an art. Too low and you get this exception, but too high and node.js itself will segfault. Note that a correct value may not exist for this app, meaning that it is possible that this app cannot be analyzed using the code analyzer.\n\nThe results that are normally displayed inside of studio are just HTML files and will be put in the directory specified. Open the index.html file inside that directory to see the results.\n",
					"updateAuthor": {
						"name": "bhughes",
						"key": "bhughes",
						"displayName": "Bryan Hughes",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2013-07-11T16:59:02.000+0000",
					"updated": "2013-07-11T16:59:02.000+0000"
				},
				{
					"id": "261458",
					"author": {
						"name": "mxia",
						"key": "mxia",
						"displayName": "Michael Xia",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "Hi Leor,\n\nCould you have the customer try enabling one option at a time in the Code Analyzer preference page to see if code analyzer could complete?\n",
					"updateAuthor": {
						"name": "mxia",
						"key": "mxia",
						"displayName": "Michael Xia",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2013-07-11T17:12:07.000+0000",
					"updated": "2013-07-11T17:12:07.000+0000"
				},
				{
					"id": "261628",
					"author": {
						"name": "lbrenman",
						"key": "lbrenman",
						"displayName": "Leor Brenman",
						"active": true,
						"timeZone": "America/Havana"
					},
					"body": "Nam, Michael and Bryan - thanks so much for the detailed instructions. With your help, the customer is now able to run Code Analyzer from the command line and they have their results. From Studio, they had success if they turned off all options, but the results are less than useful. When they turned on just Invoke Methods, they got an error: \"Code Analaysis process exited with error code: 1\".\n\nI think we can say that for Demandware the issue is closed.\n\nThanks again!",
					"updateAuthor": {
						"name": "lbrenman",
						"key": "lbrenman",
						"displayName": "Leor Brenman",
						"active": true,
						"timeZone": "America/Havana"
					},
					"created": "2013-07-12T14:57:47.000+0000",
					"updated": "2013-07-12T14:57:47.000+0000"
				}
			],
			"maxResults": 7,
			"total": 7,
			"startAt": 0
		}
	}
}