Chrome processes are not always being killed on Cypress exit

[muhammad-st]

Current behavior

If chrome was unresponsive at the time Cypress exited, Chrome processes will not be killed/closed.

Desired behavior

chrome processes should be killed with -9 after a timeout if they were unresponsive at the time of Cypress exit.

Test code to reproduce

• Run a spec that gets chrome busy/frozen (see example below).
• kill cypress with SIGINT. (as if killed due to timeout by Jenkins)
• chrome process will detach and stay there forever.

Example Scenario

describe('big file spec', () => {
  it('should fail', () => {
    cy.visit('https://www.google.com');
    cy.writeFile('./text.txt', 'x'.repeat(100*1024*1024));
  });
});

To make sure this is making chrome busy, open inspector (while using headed mode) and try to inspect the packets in Cypress's WebSocket connections, chrome will freeze (as mentioned in #17903).

Cypress Version

8.3.0

Other

No response

[muhammad-st]

@jennifer-shehane Have you had the time to look into this?

[cypress-app-bot]

This issue has not had any activity in 180 days. Cypress evolves quickly and the reported behavior should be tested on the latest version of Cypress to verify the behavior is still occurring. It will be closed in 14 days if no updates are provided.

[cypress-app-bot]

This issue has been closed due to inactivity.