-
Notifications
You must be signed in to change notification settings - Fork 43
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
Reduce renderer memory consumption when exporting #140
Conversation
@afterxleep, @bjtitus - would you mind giving this a look? 🙇 Hopefully this change is straightforward - it seems like if there's no delegate to display a renderer's output we shouldn't bother with the output method. Yet, I do see where it's mutating A WPiOS build that includes these changes is here, but I could use your guidance if we need to test Tumblr. Thank you. |
4d715e0
to
dd7b104
Compare
MultiEditorViewController: Reload the current editor during export process
} | ||
} | ||
}) | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These changes are from #141.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested in Tumblr and seems to work.
Thanks for tracking this down!
Thank you for the review @bjtitus! |
Description
Memory consumption grows constantly when exporting multiple images due to calls to
output
in the renderer. In instances where there's no delegate to process the renderer's pixel buffer, we can avoid running the function altogether.This will help alleviate WPiOS out-of-memory crashes: