Chrome is a). not reachable in automation and b). crashing when launched manually/

[GoogleCodeExporter]

Hi Guys,

We have following setup to run automation on android devices against chrome 
browser:
- appium from source version 1.3.4
- chrome details (Session info: chrome=41.0.2272.94)\n  (Driver info: 
chromedriver=2.14.313457) on mac os 
- nexus 5 with Android version 5.0
- Android Debug Bridge version 1.0.31 and 1.0.32

In the automation scripts we use cucumber with testng executing by maven. We 
have noticed that during regression test suite it often fails due to:

log from appium: 

info: [debug] Responding to client with error: 
{"status":100,"value":{"message":"An error occurred","origValue":"chrome not 
reachable\n  (Session info: chrome=41.0.2272.94)\n  (Driver info: 
chromedriver=2.14.313457 
(3d645c400edf2e2c500566c9aa096063e707c9cf),platform=Mac OS X 10.10.2 
x86_64)"},"sessionId":"729941844d1ad4c8ad1ea617fc8af24c"} 

The point of failure often varies but once it's hit, all following tests 
quickly fail reporting the above.

We have done number of investigation to pin point this issue which led us to 
exclude appium software and point towards chromedriver as a possible cause of 
failure. 

We think it might be related to some memory leak or app management in the os / 
chrome.
One more interesting thing is once the issue is hit, starting manually chrome 
is crashing the app (or starting chrome and choosing menu dots). 

After device restart it seems to be fine until we hit the issue again.

Let me know if you need more info to assist to debug this issue.

Thanks a lot in advance.

Cheers,
Ben and Tomasz

Original issue reported on code.google.com by tbor...@gmail.com on 17 Mar 2015 at 3:33

[GoogleCodeExporter]

Could you please provide a test case written directly using chromedriver, and 
without appium. This would help us to reproduce & investigate further.

Original comment by gmanikp...@chromium.org on 17 Mar 2015 at 11:54

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

So this morning I configured chromedriver without appium run the whole suite of 
tests. 

First run went smoothly without any issues, in the middle of the second run 
some tests randomly started to fail. I let it run and it hit the stage where 
each time chrome was crashing after loading the page. Even starting chrome 
manually causing issues like:
- tapping on the Search url input field it doesn't bring the keyboard up.

Im not sure if this is related directly to chromedriver not cleaning the memory 
somehow or internal chrome issue or KitKat OS. 

Testing suite has 100 scenarios, so each time new scenario starts chrome opens 
too, when scenario finishes chrome closes. All test cases are quite simple: 
opening browser, navigating to the website, login, tap buttons, check if 
elements exist etc. 

Any ideas? Is there anything else I could try to help you investigate? 

Original comment by tbor...@gmail.com on 18 Mar 2015 at 3:16

[GoogleCodeExporter]

Thank you for trying it out with chromedriver. 
We are setting up the test suite, and will get back to you soon!

Original comment by gmanikp...@chromium.org on 20 Mar 2015 at 10:24

[GoogleCodeExporter]

We were able to reproduce the issue but is very intermittent.  It looks more 
like a crash on chrome app side rather than chromedriver. We are investigating 
the issue further.

Original comment by gmanikp...@chromium.org on 24 Mar 2015 at 11:49

• Changed state: Untriaged

[GoogleCodeExporter]

Thanks guys, glad you were able to reproduce the problem, please keep us 
updated with the progress.

Original comment by tbor...@gmail.com on 25 Mar 2015 at 9:05

[GoogleCodeExporter]

Original comment by samu...@chromium.org on 31 Mar 2015 at 11:45

• Changed state: Available
• Added labels: OS-Android, Pri-2