[🐛 Bug]: Unable to hide DevTools listening on ws://127.0.0.1:53288/devtools/browser/5bc00fe8-5dea-4518-b602-70fae6c2378c

[aamiralidev]

What happened?

I wrote a general automation script to take a few input parameters from users using PySide6 and then use Selenium to run the automation. Then to ship this, I used auto-py-to-exe with a simple 3 options path to the file, onedir, and windowed. After compilation, I ran the exe and it works fine except for some console windows that it shows and I don't want users to see those extra console windows. I tried to set the log level to CRITICAL, FATAL, and OFF through different os, logging, and Selenium web driver options. I successfully reduced logs to 1 line but this still shows the annoying console window that I want to hide. I'm attaching the screenshot of one such window, the other passes so quickly.

How can we reproduce the issue?

Steps to reproduce issue
1. Create a sample PySide6 window
2. Hide it and create a selenium webdriver (Edge in this case)
3. run some random script or just put it to sleep
4. compile it using auto-py-to-exe
5. run it, you'll observer that a console window like one in screenshot shows before opening browser and it stays till the end of browser session

Relevant log output

DevTools listening on ws://127.0.0.1:53288/devtools/browser/5bc00fe8-5dea-4518-b602-70fae6c2378c

Operating System

Windows 11

Selenium version

4.10.0

What are the browser(s) and version(s) where you see this issue?

Microsoft Edge Version 114.0.1823.37 (Official build) (64-bit)

What are the browser driver(s) and version(s) where you see this issue?

EdgeDriver 114.0.1823.37 (Official build) (64-bit)

Are you using Selenium Grid?

No

[github-actions]

@aamirali-dev, thank you for creating this issue. We will troubleshoot it as soon as we can.

---

Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

[titusfortner]

We just merged #12103 which fixes this. By default, stderr/stdout for the whole chromedriver process should go to dev/null including that line.

[titusfortner]

Oh, and you also want to set the creation flag — #12138 (comment)

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.