automation - Chrome Instances don't close after running Test Case in Protractor

Question

When I run the test multiple times so Chrome instances do not close due to which PC utilization tends to 100%. So, I have to end Chrome instances manually. There might be some way to handle this?

Solution :

chromeOptions: {
  args: ["--disable-gpu"]
},

In Configuration file "Disable-gpu" is responsible to disable acceleration of chrome whenever there is some problem in rendering(in-case of failure).

Answer 1

By default protractor closes chrome instances after test execution unless the test fails in an irreconcilable way. So try to reset your protractor.conf.js settings back to default