{
	"id": "170436",
	"key": "DAEMON-186",
	"fields": {
		"issuetype": {
			"id": "1",
			"description": "A problem which impairs or prevents the functions of the product.",
			"name": "Bug",
			"subtask": false
		},
		"project": {
			"id": "12519",
			"key": "DAEMON",
			"name": "Appcelerator Daemon"
		},
		"fixVersions": [],
		"resolution": null,
		"resolutiondate": null,
		"created": "2017-11-23T13:06:45.000+0000",
		"priority": {
			"name": "Trivial",
			"id": "5"
		},
		"labels": [],
		"versions": [],
		"issuelinks": [],
		"assignee": {
			"name": "kkolipaka",
			"key": "kkolipaka",
			"displayName": "Kondal Kolipaka",
			"active": false,
			"timeZone": "America/Los_Angeles"
		},
		"updated": "2020-02-13T07:03:45.000+0000",
		"status": {
			"description": "The issue is open and ready for the assignee to start work on it.",
			"name": "Open",
			"id": "1",
			"statusCategory": {
				"id": 2,
				"key": "new",
				"colorName": "blue-gray",
				"name": "To Do"
			}
		},
		"components": [],
		"description": "When the daemon is not already started and we launch studio then a lot of flicker is noticed as if few independent windows trying to open and close.\r\nThis seems to happen when dashboard starts to launch upon studio launch and hence requests to daemon are being sent for start and system-info\r\n\r\nIf the daemon is already started or we try to restart studio the flicker is not noticed.",
		"attachment": [],
		"flagged": false,
		"summary": "Windows OS: Lot of flicker after launching studio when daemon is not already started ",
		"creator": {
			"name": "ssekhri",
			"key": "ssekhri",
			"displayName": "Satyam Sekhri",
			"active": true,
			"timeZone": "America/Los_Angeles"
		},
		"subtasks": [],
		"reporter": {
			"name": "ssekhri",
			"key": "ssekhri",
			"displayName": "Satyam Sekhri",
			"active": true,
			"timeZone": "America/Los_Angeles"
		},
		"environment": "OS: Win 10 Pro\r\nStudio: 5.0.0 (development branch code)\r\nAppc CLI: 7.0.0-master.45\r\nAppcd: 1.0.0-22",
		"comment": {
			"comments": [
				{
					"id": "431216",
					"author": {
						"name": "kkolipaka",
						"key": "kkolipaka",
						"displayName": "Kondal Kolipaka",
						"active": false,
						"timeZone": "America/Los_Angeles"
					},
					"body": "[~eharris] [~cbarber] I've seen this issue when we start the daemon from the terminal from the Windows machine. Can you guys please check this.",
					"updateAuthor": {
						"name": "kkolipaka",
						"key": "kkolipaka",
						"displayName": "Kondal Kolipaka",
						"active": false,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2017-11-23T13:46:56.000+0000",
					"updated": "2017-11-23T13:46:56.000+0000"
				},
				{
					"id": "431217",
					"author": {
						"name": "eharris",
						"key": "eharris",
						"displayName": "Ewan Harris",
						"active": true,
						"timeZone": "Europe/Dublin"
					},
					"body": "Looked at this a little and believe it's due to use spawning appcd as a detached process (so this doesnt happen during a gulp watch, or appcd start --debug)\r\n\r\nI think as we're spawning off the node process there we're at the whim of node spawning the console window it's a well known issue [pm2|https://github.com/Unitech/pm2/issues/2182], [node|https://github.com/nodejs/node/issues/7653], we added windowsHide which stopped the consoles from staying around (DAEMON-99) but the flash stuck around.\r\n\r\nI'm gonna leave this to Chris as I vaguely remember him mentioning that it's possible he's solved this issue in titanium at some point, ultimately though I think a nodew.exe similar to javaw.exe might solve this properly but there is [little movement|https://github.com/nodejs/node/issues/556]",
					"updateAuthor": {
						"name": "eharris",
						"key": "eharris",
						"displayName": "Ewan Harris",
						"active": true,
						"timeZone": "Europe/Dublin"
					},
					"created": "2017-11-23T14:41:37.000+0000",
					"updated": "2017-11-23T14:41:37.000+0000"
				},
				{
					"id": "431303",
					"author": {
						"name": "cbarber",
						"key": "cbarber",
						"displayName": "Chris Barber",
						"active": true,
						"timeZone": "America/Chicago"
					},
					"body": "I'm not sure how to address this other than Studio blocking on starting the daemon and querying the system-info as to not do too much at one time, which is not ideal.\r\n\r\nThe thing I was mentioning to Ewan was about suppressing the console window when launching the Android emulator. It's not really applicable here.",
					"updateAuthor": {
						"name": "cbarber",
						"key": "cbarber",
						"displayName": "Chris Barber",
						"active": true,
						"timeZone": "America/Chicago"
					},
					"created": "2017-11-27T16:07:33.000+0000",
					"updated": "2017-11-27T16:07:33.000+0000"
				}
			],
			"maxResults": 3,
			"total": 3,
			"startAt": 0
		}
	}
}