Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Browser TaskQueue is disposed when Page closed/disposed
See original GitHub issueDescription
It’s is more a questions than an issue.
I’m trying to reuse browser instance , the problem is that when first page is disposed the TaskQueue of the browser instance disposed as well as a result making screenshots is impossible for the next created page of the same browser instance ->
it’s throws the semaphore has been disposed exception.
I wonder if it’s an intended behavior ?
Thanks!
Versions
- PuppeteerSharp 6.0.0
- .NET 5.
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Disposing a Page causes a warning. Is this an issue?
LaunchAsync(options, factory); Page page = await browser.NewPageAsync(); await page.CloseAsync(); page.Dispose();. The last statement (page.
Read more >Use Page.DisposeAsync and Browser. ...
Not sure but after I change to use Dispose() seems these chrome process close ... LogInformation("browser is disposing"); await Page.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@qstarin I can push a version tomorrow.
Any chance of a point release to push this out? I’m blocked from updating to v6 due to this error.