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 doesnt open #2061

Closed
veighthedev opened this issue Apr 30, 2020 · 15 comments
Closed

[BUG] Firefox doesnt open #2061

veighthedev opened this issue Apr 30, 2020 · 15 comments
Assignees

Comments

@veighthedev
Copy link

veighthedev commented Apr 30, 2020

No description provided.

@veighthedev veighthedev changed the title [BUG] [BUG] Firefox doesnt open Apr 30, 2020
@pavelfeldman
Copy link
Member

Could you set DEBUG=pw:browser* and paste errors it reports?

@pavelfeldman
Copy link
Member

Yes, that would be

"env": {"DEBUG":"pw:browser*"},

@pavelfeldman
Copy link
Member

It claims it can't read the profile directory that was created for it... Could you check that you can create folders under AppData\Local\Temp? (basically the -profile option that it passes)

@veighthedev
Copy link
Author

I can create folders under AppData\Local\Temp.

@veighthedev
Copy link
Author

image

As you can see, it creates a folder in the Temp folder.

@veighthedev
Copy link
Author

veighthedev commented May 3, 2020

If someone else gets the error, set a timeout of 300-400ms before getting the page and it will work

@veighthedev veighthedev reopened this May 3, 2020
@veighthedev
Copy link
Author

But since this isnt a very reliable fix, the bug is still existing

@aesyondu
Copy link
Contributor

aesyondu commented May 5, 2020

Have you tried deleting and re-downloading the firefox browser? I'm thinking it could be a corrupt browser download.

Also does the bug exist in other versions, 0.16, 0.17 perhaps?

@veighthedev
Copy link
Author

I reinstalled it multiple times and it also happes in older versions.

@0x446f6d
Copy link

  • 1 ^ I experienced the bug as well. While the timeout fixed the issue, it isn't ideal.

@pavelfeldman
Copy link
Member

@SentoxAIO: Which timeout fixes it? After launch before creating the context?

@veighthedev
Copy link
Author

veighthedev commented May 28, 2020

It worked for me with a delay of 300-400ms before creating the context

@veighthedev
Copy link
Author

Seems like its fixed. Thanks for your work!

@thenengah
Copy link

  await page.waitForTimeout(500);
  await page.goto("https://example.com/")

^ The timeout approach also worked for me. I only found this in Firefox but could be in other browsers.

I think what's happening is that page.goto doesn't care about the current state, but something in the current state like a pending req is aborted when goto is triggered.

@vogler
Copy link

vogler commented Feb 2, 2023

Had the same problem with goBack, solved it with waitForLoadState instead of waitForTimeout:

// ...
await page.waitForLoadState(); // needed
await page.goBack(); // without the wait above got Error: NS_BINDING_ABORTED; same for goto()

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

7 participants