0.4.3 - #7
Merged
Merged
0.4.3#7
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Picking a very large file to attach crashed the app: it read the whole file into memory (arrayBuffer) before anything could stop it, so a ~500MB video exhausted RAM and the OS killed the app. Attachments are now capped at 50 MB, checked by File.size before any read, and anything larger is refused up front with a message (EN + ES). A setPendingAttach backstop enforces the same cap on the share and camera paths. The e2e attaches a 51MB file and asserts it is refused with no entry and no crash. Found by a tester on !48333. Bumps to 0.4.3.