You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Consider the following test application (.NET Core):
using System;
using System.IO;
using BSL = BrotliSharpLib;
using System.IO.Compression;
namespace BrotliTest
{
class Program
{
static void Main(string[] args)
{
using (var mem = new MemoryStream())
{
using (var brotli = new BSL.BrotliStream(mem, CompressionMode.Compress))
{
}
}
Console.ReadLine();
}
}
}
When executed, you will see a 300 MB process memory spike in Visual Studio's Diagnostics tool window. This only happens on first instantiation of a BrotliStream. Is there a way to improve memory management in this regard?
The text was updated successfully, but these errors were encountered:
Kaliumhexacyanoferrat
changed the title
First instances spikes with 300 MB memory usage
First instance spikes with 300 MB memory usage
Apr 3, 2019
Consider the following test application (.NET Core):
When executed, you will see a 300 MB process memory spike in Visual Studio's Diagnostics tool window. This only happens on first instantiation of a
BrotliStream
. Is there a way to improve memory management in this regard?The text was updated successfully, but these errors were encountered: