Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Firefox is too slow with going to page and getting content #5839

Closed
hahyes opened this issue Mar 16, 2021 · 2 comments
Closed

[BUG] Firefox is too slow with going to page and getting content #5839

hahyes opened this issue Mar 16, 2021 · 2 comments
Assignees

Comments

@hahyes
Copy link

hahyes commented Mar 16, 2021

Context:

  • Playwright Version: last release, from Nuget package: 0.192
  • Operating System: Windows 10
  • Node.js version: v12.18.3
  • Browser: Firefox
  • Extra: Used on .NET Core 3.1 and Visual Studio 2019

Code Snippet

   //earlier is just standard initialization of Firefox browser, context and page from docs

   await page.GoToAsync("https://allegro.pl");

   string html = await page.GetContentAsync();

Describe the bug

Hi there,

I tried to use Firefox browser for loading page and getting whole HTML code. Problem is... this is slow. Incredibly slow.

These two lines take in my test from 17 to 25 seconds, measured with Stopwatch.
On Webkit it's between 4 and 6 seconds, depends on using or not VPN.

How is this possible?

Version of browsers:

  • Firefox: 86.0b10
  • Webkit: 14.1

I didn't try downgrade of Playwright. I'm fine with using Webkit for now, but wanted to report that something is wrong with Firefox here.

@hahyes hahyes changed the title [BUG] [BUG] Firefox is too slow with going to page and getting content Mar 16, 2021
@aslushnikov
Copy link
Collaborator

@hahyes is this a regression? Could you please try an older version, e.g. 0.180.0?

I'm fine with using Webkit for now, but wanted to report that something is wrong with Firefox here.

Thank you for the heads up! ❤️

@pavelfeldman
Copy link
Member

We need more information to address this issue. Please file a new one with the response to above if this is still a case!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants