You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
async captureScreenshot is about ~40x slower than the synchronous version (taking a 800x600 screenshot takes ~20s vs 500ms). This is because captureScreenshot returns a Stream containing the bytes making up the png screenshot and we have to call Stream.toList() to write the screenshot to a file. Compared to returning the list directly, it is 5000x slower in a test. (100x slower because of wrapping it in a Stream and async_/yield_ and 50x slower because of unittest & stack_trace).
The suggested solution is to add a captureScreenshotAsList method back that returns a simple List.
See also captureScreenshotAsBase64 #112
The text was updated successfully, but these errors were encountered:
async captureScreenshot is about ~40x slower than the synchronous version (taking a 800x600 screenshot takes ~20s vs 500ms). This is because captureScreenshot returns a Stream containing the bytes making up the png screenshot and we have to call Stream.toList() to write the screenshot to a file. Compared to returning the list directly, it is 5000x slower in a test. (100x slower because of wrapping it in a Stream and async_/yield_ and 50x slower because of unittest & stack_trace).
The suggested solution is to add a captureScreenshotAsList method back that returns a simple List.
See also captureScreenshotAsBase64 #112
The text was updated successfully, but these errors were encountered: