Firefox is not closed after tests are finished

[rkrisztian]

Bug report

Issue is similar to #4408, but I'm having a different issue now.

• Node Version: 6.10.3
• Protractor Version: 5.1.2
• Angular Version: 4.2.6
• Browser(s): Firefox 52.2.0 (64-bit)
• Operating System and Version RHEL 6
• Your protractor configuration file: Angular CLI 1.2.0 defaults +

    capabilities: {
        browserName: 'firefox'
    },
    directConnect: false,
    localSeleniumStandaloneOpts: {
        jvmArgs: ['-Dwebdriver.gecko.driver=/home/rkrisztian/projects/testProject/node_modules/protractor/node_modules/webdriver-manager/selenium/geckodriver-v0.18.0']
    },
    onComplete: function() {
        browser.close();
    }

• A relevant example test: Not needed, issue is driver-specific.
• Output from running the test:

Executed 4 of 4 specs SUCCESS in 13 secs.
[11:52:05] I/local - Shutting down selenium standalone server.
[11:52:05] I/launcher - 0 instance(s) of WebDriver still running
[11:52:05] I/launcher - firefox #01 passed

• Steps to reproduce the bug:

When I comment out the onComplete block, Firefox will keep running after the tests have all been executed.

I also tried marionette: true, but the result was the same.

[cnishina]

Have you tried a more recent version of Firefox?

[jan-molak]

I noticed a similar issue with forked Chrome browsers where they stay alive even after the test is finished. I reported that as an issue around restarting the browser #4315, but it feels related to how Protractor handles closing browsers in general?

[wswebcreation]

@rkrisztian

Is this issue still valid? I've tested this with the example project and I don't have any problems with these settings

• OSX 10.12.6
• NodeJS 6.11.1
• Firefox 55 + 56
• Geckodriver 0.19.0

And the browser is closed. Can you verify that? If there's no activity till next week I assume it's not happening anymore and I'll close the issue.

[wswebcreation]

Going to close this due to inactivity