Nighwatch does not exit properly. Chromedriver still in execution. Possible solution provided

I’m submitting a … (check one with “x”)

[X] bug report
[ ] feature request
[ ] support request => Please do not submit support request here, instead use https://groups.google.com/d/forum/nightwatch-cucumber

Current behavior Nighwatch does not exit properly. Browser and chromedriver still in execution, even thought an error ocurred. After Ctrl+c chromedriver process is still in execution

Expected/desired behavior Nightwatch-cucumber executes the right nightwatch termination code. That way, the nightwatch & chromedriver process will terminate.

Reproduction of the problem If the current behavior is a bug or you can illustrate your feature request better with an example, please provide the steps to reproduce and if possible a minimal demo of the problem via https://c9.io, http://www.koding.com, https://www.nitrous.io or similar.

git clone https://github.com/kabomi/nw-cucumber-not-exiting.git
cd nw-cucumber-not-exiting
npm install
nightwatch -c nightwatch-conf.js

Hint to a solution An example of what’s probably needed to be done

What is the expected behavior? Nightwatch-cucumber executes the right nightwatch termination code. That way, the nightwatch & chromedriver process will terminate.

What is the motivation / use case for changing the behavior? Jenkins builds timeout because of nightwatch process not exiting.

Please tell us about your environment: MacOs Sierra 10.12.5

• output of the following command from your project root npm ls nightwatch cucumber nightwatch-cucumber && node --version

├── cucumber@2.3.1
├── nightwatch@0.9.16
└── nightwatch-cucumber@7.1.10

v6.9.1

[viveksgit]

@mucsi96 the above issue occurs with v 9.1.2

[mucsi96]

Fixed in https://github.com/mucsi96/nightwatch-cucumber/releases/tag/v8.0.6 .Thanks for your feedback! Thanks to You I improved and simplified the error handling a lot! 🎉