OutOfMemoryException on .NET Core when computing MD5 hash
See original GitHub issueOutOfMemoryException at
at System.IO.MemoryStream.ToArray()
at Microsoft.WindowsAzure.Storage.Core.Util.MD5Wrapper.ComputeHash()
at Microsoft.WindowsAzure.Storage.Blob.BlobWriteStream.<CommitAsync>d__9.MoveNext()
Looking at that code I see it’s doing ToArray
on the MemoryStream
it is using.
With that I can’t upload files of significant size without turning off the MD5 checksums.
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Hash from different files is always the same
Let's create a function that will receive an IFormFile , compute the MD5 hash of its contents then return the hash value as...
Read more >OutOfMemoryException caused by user-code in ASP.NET ...
Describe the bug. There appears to be a global try/catch in some places inside ASP.NET Core. When allocating too much ram such that...
Read more >OutOfMemoryException Class (System)
The exception that is thrown when there is not enough memory to continue the execution of a program.
Read more >Computing File Hashes in C# - Gigi Labs - Daniel D'Agostino
NET that you can use, including MD5, SHA256, and others. A hash gives you a way to verify whether a file has been...
Read more >Error in WuaDataProvider: System.OutOfMemoryException
It happens usually on Server systems with slightly different .NET memory engagement than Workstations. This is a system level issue
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi @dabide,
The fix for this particular feature will be provided once Mono 5.0 (stable) is released which will tentatively be sometime in May.
Additionally, we are considering the option of adding a new target to our Nuget package for Xamarin/Mono to add tolerance for cases like this until NetStandard implementation on all platforms are stabilized.
Thanks, Elham
Thanks @erezvani1529