Hi everyone!
We are running Hangfire 1.8.14 with Hangfire.PostgreSql 1.20.9 on .NET Core 8.
It seems that there is a memory leak that only occurs when running it in a linux container deployed to Azure container apps.
When run locally we did not observe the behavior.
Currently we have the following projects:
API - with the endpoints used to enqueue new jobs,
HangfireServer - ASP.NET Core app where Hangfire is hosted and,
Jobs - a seperate project/dll that contiains the classes with methods that represent the jobs.
The API only calls IBackgroundJobClient.Enqueue() and does no further processing.
So for example I have a simple class:
public class KillMemoryJob
{
public async Task Run()
{
long bytesToAllocate = (long)(1.5 * 1024 * 1024 * 1024);
byte[] memory = new byte[bytesToAllocate];
for (long i = 0; i < memory.Length; i++)
{
memory[i] = 0;
}
Console.WriteLine("Successfully allocated 1.5 GB of memory.");
await Task.Delay(1000 * 60 * 5); // wait five minutes to finish
}
}
that allocates 1.5GB of memory.
The API endpoint is defined as:
app.MapGet("api/debug/kill-memory",
(IBackgroundJobClient backgroundJobClient) =>
{
string jobId = backgroundJobClient.Enqueue<KillMemoryJob>(zbj =>
zbj.Run());
return Results.Ok(jobId);
});
The behavior I expect to observe is that the API enqueues the job, the server takes it and starts processing. After the processing finishes and the Run() method exits (after a five minute delay), the allocated memory is released.
That works as expected when I run it locally on my Windows machine, but when deployed to Azure Container Apps the memory never gets released.
I can provide a dump file if that would help figure out the issue.
