A new session could not be created. (Original error: An error occurred (Original error: chrome not reachable

Issues/Bugs
1

Currently I am using Samsung device to run my mobile web automation.Every time When I run the test the following error is showing and chrome browser not responding.

Chrome version: 45+
android version: 5.0.1
appium version: 1.4.13
chrome driver version 2.19

info: JSONWP Proxy: Proxying [POST /session] to [POST http://127.0.0.1:9515/wd/hub/session] with body: {“desiredCapabilities”:{“chromeOptions”:{“androidPackage”:“com.android.chrome”,“androidDeviceSerial”:“4d006312964a40fd”}}}
info: JSONWP Proxy: Got response with status 200: {“sessionId”:“331a441905c5a7a3dd4dae8d1110f721”,“status”:100,“value”:{“message”:"chrome not reachable\n (Driver info: chromedriver=2.19.346078 (6f1f0cde889532d48ce8242342d0b84f94b114a1),platform=Wind…
info: JSONWP Proxy: Proxying [POST /session] to [POST http://127.0.0.1:9515/wd/hub/session] with body: {“desiredCapabilities”:{“chromeOptions”:{“androidPackage”:“com.android.chrome”,“androidDeviceSerial”:“4d006312964a40fd”}}}
info: [debug] [BOOTSTRAP] [debug] Emitting system alert message
info: [debug] Emitting alert message…
info: [debug] [BOOTSTRAP] [debug] Emitting system alert message
info: [debug] Emitting alert message…
info: JSONWP Proxy: Got response with status 200: {“sessionId”:“32eb66fb8c4e4dd463cb45d444ebe1a0”,“status”:100,“value”:{“message”:"chrome not reachable\n (Driver info: chromedriver=2.19.346078 (6f1f0cde889532d48ce8242342d0b84f94b114a1),platform=Wind…
info: JSONWP Proxy: Proxying [POST /session] to [POST http://127.0.0.1:9515/wd/hub/session] with body: {“desiredCapabilities”:{“chromeOptions”:{“androidPackage”:“com.android.chrome”,“androidDeviceSerial”:“4d006312964a40fd”}}}
info: JSONWP Proxy: Got response with status 200: {“sessionId”:“6f70cb4dace8387b653f0842a6f7ab30”,“status”:21,“value”:{“message”:"timeout: Adb command timed out after 30 seconds\n (Driver info: chromedriver=2.19.346078 (6f1f0cde889532d48ce8242342d0b…
info: JSONWP Proxy: Proxying [POST /session] to [POST http://127.0.0.1:9515/wd/hub/session] with body: {“desiredCapabilities”:{“chromeOptions”:{“androidPackage”:“com.android.chrome”,“androidDeviceSerial”:“4d006312964a40fd”}}}
info: JSONWP Proxy: Got response with status 200: {“sessionId”:“85a43fb81158d950371065c1736103e1”,“status”:100,“value”:{“message”:"chrome not reachable\n (Driver info: chromedriver=2.19.346078 (6f1f0cde889532d48ce8242342d0b84f94b114a1),platform=Wind…
info: Chromedriver: Changed state to ‘stopped’
error: Chromedriver: Chromedriver exited unexpectedly with code null, signal SIGTERM
error: Chromedriver: Error: An error occurred (Original error: chrome not reachable
(Driver info: chromedriver=2.19.346078 (6f1f0cde889532d48ce8242342d0b84f94b114a1),platform=Windows NT 6.1 SP1 x86_64))
at JWProxy.command$ (lib/proxy.js:149:15)
at tryCatch (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-chromedriver\node_modules\babel-runtime\regenerator\runtime.js:67:40)
at GeneratorFunctionPrototype.invoke [as _invoke] (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-chromedriver\node_modules\babel-runtime\regenerator\runtime.js:294:22)
at GeneratorFunctionPrototype.prototype.(anonymous function) [as next] (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-chromedriver\node_modules\babel-runtime\regenerator\runtime.js:100:21)
at GeneratorFunctionPrototype.invoke (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-chromedriver\node_modules\babel-runtime\regenerator\runtime.js:136:37)
at GeneratorFunctionPrototype.b (domain.js:183:18)
at lib$es6$promise$$internal$$tryCatch (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\es6-promise\dist\es6-promise.js:331:16)
at lib$es6$promise$$internal$$invokeCallback (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\es6-promise\dist\es6-promise.js:343:17)
at lib$es6$promise$$internal$$publish (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\es6-promise\dist\es6-promise.js:314:11)
at Object.lib$es6$promise$asap$$flush [as _onImmediate] (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\es6-promise\dist\es6-promise.js:125:9)
at processImmediate [as _immediateCallback] (timers.js:330:15)
{ [Error: An error occurred (Original error: chrome not reachable
(Driver info: chromedriver=2.19.346078 (6f1f0cde889532d48ce8242342d0b84f94b114a1),platform=Windows NT 6.1 SP1 x86_64))]
status: 100,
value: { message: ‘chrome not reachable\n (Driver info: chromedriver=2.19.346078 (6f1f0cde889532d48ce8242342d0b84f94b114a1),platform=Windows NT 6.1 SP1 x86_64)’ },
httpCode: 200 }
info: Chromedriver stopped unexpectedly on us, shutting down then calling back up with the on-die callback
info: [debug] Cleaning up appium session
info: [debug] Error: An error occurred (Original error: chrome not reachable
(Driver info: chromedriver=2.19.346078 (6f1f0cde889532d48ce8242342d0b84f94b114a1),platform=Windows NT 6.1 SP1 x86_64))
at JWProxy.command$ (lib/proxy.js:149:15)
at tryCatch (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-chromedriver\node_modules\babel-runtime\regenerator\runtime.js:67:40)
at GeneratorFunctionPrototype.invoke [as _invoke] (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-chromedriver\node_modules\babel-runtime\regenerator\runtime.js:294:22)
at GeneratorFunctionPrototype.prototype.(anonymous function) [as next] (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-chromedriver\node_modules\babel-runtime\regenerator\runtime.js:100:21)
at GeneratorFunctionPrototype.invoke (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-chromedriver\node_modules\babel-runtime\regenerator\runtime.js:136:37)
at GeneratorFunctionPrototype.b (domain.js:183:18)
at lib$es6$promise$$internal$$tryCatch (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\es6-promise\dist\es6-promise.js:331:16)
at lib$es6$promise$$internal$$invokeCallback (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\es6-promise\dist\es6-promise.js:343:17)
at lib$es6$promise$$internal$$publish (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\es6-promise\dist\es6-promise.js:314:11)
at Object.lib$es6$promise$asap$$flush [as _onImmediate] (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\es6-promise\dist\es6-promise.js:125:9)
at processImmediate [as _immediateCallback] (timers.js:330:15)
info: [debug] Responding to client with error: {“status”:33,“value”:{“message”:“A new session could not be created. (Original error: An error occurred (Original error: chrome not reachable\n (Driver info: chromedriver=2.19.346078 (6f1f0cde889532d48ce8242342d0b84f94b114a1),platform=Windows NT 6.1 SP1 x86_64)))”,“status”:100,“value”:{“message”:“chrome not reachable\n (Driver info: chromedriver=2.19.346078 (6f1f0cde889532d48ce8242342d0b84f94b114a1),platform=Windows NT 6.1 SP1 x86_64)”},“httpCode”:200,“origValue”:“An error occurred (Original error: chrome not reachable\n (Driver info: chromedriver=2.19.346078 (6f1f0cde889532d48ce8242342d0b84f94b114a1),platform=Windows NT 6.1 SP1 x86_64))”},“sessionId”:null}
info: ← POST /wd/hub/session 500 232090.361 ms - 668
info: [debug] [BOOTSTRAP] [debug] Got data from client: {“cmd”:“shutdown”}
info: [debug] [BOOTSTRAP] [debug] Got command of type SHUTDOWN
(Driver info: chromedriver=2.19.346078 (6f1f0cde889532d48ce8242342d0b84f94b114a1),platform=Windows NT 6.1 SP1 x86_64))
info: [debug] [BOOTSTRAP] [debug] Returning result: {“status”:0,“value”:“OK, shutting down”}
info: [debug] [BOOTSTRAP] [debug] Closed client connection
info: [debug] Sent shutdown command, waiting for UiAutomator to stop…
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: numtests=1
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=.
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: id=UiAutomatorTestRunner
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: test=testRunServer
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: class=io.appium.android.bootstrap.Bootstrap
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: current=1
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: 0
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=
info: [debug] [UIAUTOMATOR STDOUT] Test results for WatcherResultPrinter=.
info: [debug] [UIAUTOMATOR STDOUT] Time: 225.415
info: [debug] [UIAUTOMATOR STDOUT] OK (1 test)
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: -1
info: [debug] UiAutomator shut down normally
info: [debug] executing cmd: C:\Users\srajagop\AppData\Local\Android\android-sdk\platform-tools\adb.exe -s 4d006312964a40fd shell “am force-stop com.android.chrome”
info: [debug] Stopping logcat capture
info: [debug] Logcat terminated with code null, signal SIGTERM
info: [debug] Cleaning up appium session

2

Better to close node.exe from your task manager once (Windows 7-Press ctrl+alt+del button for task manager).

3

Also please post your code.

4 
I am also facing the same problem.
 code:
Set<String> contextNames = driver.getContextHandles();
for (String contextName : contextNames)

{
System.out.println(contextName);
if (contextName.contains(“WEBVIEW”))
{
driver.context(contextName);

	}

}