-
Notifications
You must be signed in to change notification settings - Fork 73
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
support big files (>250 MB) #12
Comments
Hello, It has to do with some files not Hashing the SHA256 Digest properly on client-side JS library crypto.js |
The problem is in the FileReader Javascript function. Chrome 45, for example, does not allow files bigger than 261 MB. Sadly, e.target.result returns an empty string, without any other error. This means that all files larger than 261 MB are returning e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855, which is the SHA256 hash of the empty string. I have tried myself to stop the process if data=="" , but it works at first and in later tests it brings the unwelcome Chrome message "Aw, Snap!". So maybe it is better to just check the size of the file being evaluated first and inform the user that the maximum acceptable size is 250 MB. |
Hey @Nd60 thanks for reporting that back. It looks like that's the problem 👍 |
No description provided.
The text was updated successfully, but these errors were encountered: