[Bug]: UI seems to lock on Windows making tests time out about playwright HOT 7 CLOSED

I'll close this issue, because there is no action item for Playwright right now. If you come up with some new findings, please file a new issue and link to this one, so we can continue the discussion.

from playwright.

Seems like problem also exists when running from command line, but with smaller impact:

from playwright.

@pbrzosko I have played with your repro a bit. Things are slowing down indeed, but some of that is expected due to increased parallelization between single worker and many workers. However, I did not reach 10 seconds.

UI mode is noticeably slower. I think this is due to trace being recorded by UI mode, and disk access slowing everything down. Perhaps the shared disk access may even slow down all workers in parallel, which looks like "locking effect".

from playwright.

How about every worker using its own directory to gather trace and then everything is combined at the end of the run?
Why it doesn't happen on OSX?
What times do you get? It might be some of the company installed software that spoils things but we have no idea where to look?

from playwright.

How about every worker using its own directory to gather trace and then everything is combined at the end of the run?

Each worker has its own directory already.

Why it doesn't happen on OSX?

I guess the filesystem is implemented differently? Note that it was just my first idea, and the problem might be entirely different.

What times do you get?

Everything is ~1.8x slower in UI mode. Going up to 8 workers slows down each test ~2x.

It might be some of the company installed software that spoils things but we have no idea where to look?

That could easily be the case with the antivirus. You can check that by running with --workers=1 and --trace=on/--trace=off without UI mode. This way you can isolate the impact of tracing, which writes to disk, on the test timing. Something like an antivirus could slow things down significantly.

from playwright.

I will check the trace impact. But when we run with 1 worker in UI mode, times are as expected. So it seems like some locking issue which is only visible with many workers running.

from playwright.

Yyy, say that again @dgozman? You have clear evodence that tests run over 10s instead of one and you say there is nothing to do from your side?

from playwright.