E2E tests fail with Microsoft edge driver and webview2 runtime driver version 124.0.2478.51/67

51062596 60 Reputation points


we have E2E tests that run on our windows server. The Microsoft edge driver and Microsoft edge webview2 runtime drivers were updated from version 123.0.2460.97 to 124.0.2478.51/67 on April 18th and again on April 25th (respectively).

Since the upgrade the server fails and it's CPU sky rockets, without a hard reboot the server does not respond.

The STDIO streams did not close within 10 seconds of the exit event from process ''. This may indicate a child process inherited the STDIO streams and has not yet exited.

from what i understand something is not closing or not closing correctly.

the E2E tests were working prior to the upgrade of the driver.

we work with windows 2022 server datacenter

please help


Microsoft Edge
Microsoft Edge
A Microsoft cross-platform web browser that provides privacy, learning, and accessibility tools.
2,175 questions
Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,288 questions
0 comments No comments
{count} votes

Accepted answer
  1. Gyoreb Balazs 80 Reputation points

    I had the exact same problem. It was super annyoing.

    I started to update dependencies, maybe it's part of the solution. Not sure. The selenium version now I use is 4.20.0. It didn't solve the issue in itself.

    I checked the Edge arguments I use and removing the "--no-sandbox" arg, solved the problem.
    Just sharing it if you still have the issue.

    1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
  1. Jinxin Wang (Shanghai Wicresoft Co Ltd) 990 Reputation points Microsoft Vendor

    Hi @51062596,

    Based on your description, I guess the possible reason is that the updated test framework is incompatible with Edge driver or runtime, or the related process release is incomplete. So, I can give you the following four suggestions:

    1. You can move some work to the GPU (such as demanding graphics work).
    2. As you know, you can roll back the version to solve the problem.
    3. As you have already discovered, there may be incomplete or incorrect process exits. I suggest that you should capture relevant logs to locate the problem more accurately. You can check whether the test framework has generated logs.
    4. Surely, you can submit feedback. You can click "Issues" in the interface, then click "New Issue "to create a ticket.

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    Best regards,

    Jinxin Wang

    0 comments No comments