Open viveleroi opened 12 months ago
@viveleroi Unfortunately, we are not able to reproduce the issue, and we haven't seen similar complaints in the recent past. Most likely, there is something about your environment that triggers this issue - antivirus, extensions, etc.
I'll keep this issue open to see whether someone else experiences this problem and could help us with figuring out the culprit.
I will try to find more about how to reproduce it. Several users did add on to my discord question saying they had seen the same problem but they had less info than I did.
We are also facing similar issue as pointed out in all 3 below bug requests, unfortunately we are not able to share a code repo where the issue can be reproduced. https://github.com/microsoft/playwright/issues/26794 https://github.com/microsoft/playwright/issues/26671 https://github.com/microsoft/playwright/issues/26656 We are still trying to debug on what is causing the issue. When we downgraded the version to 1.33 and ran the tests again, it all works fine and the issue is not seen. From what we noticed, version 1.34 and above if any test case fails the worker/thread doesn't get closed until we manually kill the nodes in activity monitor but the browser closes and the test run is stuck.
It happens for us all the time when we run the npm script via intellij and then stop it using intellij button in the middle of the test runs we are running tests in a parallel mode and we are using windows 11
@Smrtnyk Unfortunately, we cannot figure out whether the bug is in Playwright or in IntelliJ integration without a repro. Can you share detailed repro instructions with us?
@dgozman I will try to assemble a clear repro instruction tomorrow and let you know
@dgozman I just tried it out and how it happened for me is in this sequence
"test:playwright:stable:chromium:local": "npm run test:playwright:stable:local -- -- --project=chromium --debug"
)Had to do this 2 or 3 times to accumulate orphan chromium processes in the task manager
@Smrtnyk Perhaps the issue is related to --debug
option. Let me take a look.
I see this when debugging in webstorm. The only way to kill the debugger processes is to kill webstorm.
Facing the same issue here with Windows on Parallels. Thought nothing could make the M1 warm but the always alive Chromium processes running in the background, even after quitting VSCode, ended up sucking a lot of battery and heating up the machine.
I am experiencing the same issue on Mac arm64. It takes a long time (around 5min) cpu usage reducing after pressing ctrl+c. My observation is that the longer the test, the more the number of nodes increases, and the longer it takes for the CPU to calm down.
No --debug or --headed.
For me it was all Chromium
instead of node
that you are seeing.
Hello Team. Same issue on Windows OS.
async with SEMAPHOR:
# Process the wallet asynchronously
settings = Settings()
now = int(time.time())
async with async_playwright() as p:
if wallet.proxy:
proxy = await Helper.setup_proxy(wallet.proxy)
args = [
f"--disable-extensions-except={EXTENTION_PATH}",
f"--load-extension={EXTENTION_PATH}",
"--no-sandbox", # Add any other arguments you need
'--lang=en-US', # Set language to English (United States)
]
if HEADLESS:
args.append(f"--headless=new")
context = await p.chromium.launch_persistent_context(
'',
headless=False,
args=args,
proxy=proxy,
)
// Code
await context.close()
async with LOCK:
pass
Please could you advise why the chromium driver still running even after context.close() ?
Thanks
We've been setting up Playwright for the first time and while tests work and pass, we've been noticing Chromium processes sometimes continue running and accumulate and start driving our cpu up. We were confused why our laptops were getting so warm over a week or so of work and then we noticed this:
It appears that this happens when we CTRL+C quit the testing process before it's completed, usually because we're developing and realized we made a mistake or something needs to be changed. I asked about this in discord and was advised to report a bug.
I'm using a fixture based on the example in the playwright docs for shared authentication, because we modify server state. Not sure if that has anything to do with this.
System info
Source code
playwright.config.js:
fixtures.ts:
an example test:
Steps
Expected
All processes close.
Actual
See pic above. We have to hit "End Task" in task manager for these to close properly.