Help with Closing Unresponsive Pages in PuppeteerSharp #2841
Unanswered
maurizioceravolo
asked this question in
Q&A
Replies: 1 comment
-
Just to add some information. Often it happens when Chrome has this error code: STATUS_ACCESS_VIOLATION. Then I can't interact any more with it |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello everyone,
I’m encountering a rather unusual issue while working with PuppeteerSharp in my software, which performs repetitive tasks on webpages.
The software can run smoothly for hours, but occasionally, it loses connection to the page. When this happens, every operation I attempt throws a "null reference" error.
To handle this, I create a new browser context and open a new page, which resolves the issue temporarily. However, over time, I end up with multiple open pages that consume memory, eventually making the system unresponsive.
I’ve tried using CloseAsync() followed by DisposeAsync() to close unresponsive pages, but they still seem to linger in memory.
Is there a more effective way to close these pages or any known workaround for this issue?
Thanks in advance for your help!
Beta Was this translation helpful? Give feedback.
All reactions