-
Notifications
You must be signed in to change notification settings - Fork 26.9k
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
skwasm: allocating memory until we crash! #143800
skwasm: allocating memory until we crash! #143800
Comments
For me this is:
|
I don't think this is a memory leak thing. In my repro of it, it happens immediately on the first frame, and it's trying to create an image bitmap 20 billion pixels tall, so I think that is the issue. |
I have a fix out for review for this, but it has merge conflicts because it was built on top of #140429, which had to be reverted. Relanding that is dependent on a dart issue that is being worked on. Rather than rewrite this twice, once for the old way the rendering worked and once for the new way, I'm going to wait until the Skwasm frame timing callbacks PR relands before I merge this. |
…50887) This fixes flutter/flutter#143800, where we are attempting to capture an image that is way too large. We only need to render the part of the image that will be visible in the window.
Reopen as the fix was reverted. 3rd times the charm! |
…ndow." (#51077) This fixes flutter/flutter#143800, where we are attempting to capture an image that is way too large. We only need to render the part of the image that will be visible in the window. This includes some additional fixes for regressions in the original fix.
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of |
See https://vote-dart.web.app/
The text was updated successfully, but these errors were encountered: