Asp net core 6 web api memory deployed in openshift not released


ASP.NET is a popular programming language used for building web applications. It provides a for developing websites, web services, and web APIs. In this article, we will discuss a common issue faced by developers when using ASP.NET Core 6 web API deployed in OpenShift, where memory is not released properly.

The Problem

When deploying an ASP.NET Core 6 web API in OpenShift, developers may notice that the memory used by the is not released properly. This can lead to memory leaks and issues over time. The root cause of this problem lies in the way the application is configured and managed in the OpenShift environment.


To solve this issue, we need to make some changes to the ASP.NET Core 6 web API and deployment process in OpenShift. Here are the steps to follow:

Step 1: Configure Resource Limits

OpenShift allows you to set resource limits for your application pods. By setting appropriate resource limits, you can ensure that the application does not excessive memory. To configure resource limits, you can use the following code snippet:

apiVersion: v1
kind: Pod
  name: my-app
  - name: my-app-
    : my-app-image
        memory: "512Mi"

In the above code, we have set the memory limit to 512MB. You can adjust this value based on your application's requirements.

Step 2: Implement Proper Disposal of Resources

In ASP.NET Core 6, it is important to properly dispose of resources to avoid memory leaks. Make sure that you dispose of any resources that implement the IDisposable interface. Here is an example of how to dispose of a database connection:

using (var connection = new SqlConnection(connectionString))
    // Use the connection

By using the “using” statement, the connection will be automatically disposed of when it is no longer needed.

Step 3: Enable Garbage Collection

Garbage collection is an important mechanism in .NET for reclaiming memory that is no longer in use. By , ASP.NET Core 6 uses the server garbage collector, which may not be optimal for all scenarios. To enable garbage collection, you can add the following code to your application's startup class:

public void ConfigureServices(IServiceCollection services)
    // Other configuration code

    // Enable garbage collection
    services.Configure(options =>
        options.ServerGarbageCollection = false;

By setting the “ServerGarbageCollection” option to false, you can enable the client garbage collector, which may provide better memory management in certain scenarios.

Step 4: Monitor and Optimize

After implementing the above steps, it is important to monitor your application's memory usage and performance. OpenShift provides various monitoring tools that can help you identify any memory leaks or performance bottlenecks. Use these tools to optimize your application and ensure efficient memory usage.


By following the steps outlined in this article, you can solve the issue of memory not being released properly in an ASP.NET Core 6 web API deployed in OpenShift. Proper configuration of resource limits, disposal of resources, enabling garbage collection, and monitoring can help you optimize memory usage and improve the performance of your application.

Rate this post

Leave a Reply

Your email address will not be published. Required fields are marked *

Table of Contents