ASPX templates
Version 5.x > ASPX templates > Memory Leak View modes: 
User avatar
Member
Member
matthew.lee-kenticodeveloper - 7/31/2012 4:16:56 AM
   
Memory Leak
I am investigating a memory leak issue on a Kentico 5.5 website. The website use lots of memory and keep cycle the applcation pool. I am using ANTS Memory Profiler tool (It is a great tool!) to analyse the memory now.

Basically, there are a couple of classes chewed lots of memory.

- System.LocalDataStoreElement[]
- System.string
- System.Byte[] (Files)

1. Under the Kentico Architecture, what kinds of object would be stored in the LocalStoreElement[]? Is it possible I can manage the object in this array?

2. Can I limit the capacity of file stored in the memory?


Cheers,
Matt

User avatar
Kentico Support
Kentico Support
kentico_jurajo - 7/31/2012 7:12:14 AM
   
RE:Memory Leak
Hi,

What are the memory limits set for the application pool? this seems to me more that you are hitting the limits than a memory leak. Have you tried to increase these limit to see whether the memory will grow again up to the limit or not?

What are your caching settings?

Best regards,
Juraj Ondrus

User avatar
Member
Member
matthew.lee-kenticodeveloper - 7/31/2012 6:58:55 PM
   
RE:Memory Leak
Global caching is 30 minutes. Page level caching is 5 mins. I set the memory limits on 1,000,000KB (Private Memory). Memory usage keeps growing to the limit until the app pool recycling.

This causes an issue. a page is getting some data from the database by LINQ. When the server is running out of memory, the LINQ query would catch "out of memory" exception. However, the size of the result is not big at all.

User avatar
Kentico Support
Kentico Support
kentico_jurajo - 8/2/2012 3:03:53 AM
   
RE:Memory Leak
Hi,

So, you are using caching - this means that the memory consumption is higher. When you disable the cache, do you see the memory "leak"? Have you tried to increase the memory limits - when using caching 1GB or memory may not be enough depending also ion the traffic on the site.

Best regards,
Juraj Ondrus