Asp.net session expire very soon -


I get this message many times and it seems that this is not normal, how can I fix this problem?

A worker process with a service id of '8052' service pool 'mywebsite.com' has requested a recycle because it has reached its personal bytes memory limit. "post-text" itemprop = "text">

Hi, it has not expired due to timeout, due to this memory limit, an application pool recycle It's usually too bad.

If you have complete control of your ASP.NET application, then I recommend that you profile it carefully and find out that you are allocating and not exceeding the amount of storage / release. . > It can help to understand how many times users are going in the normal usage cases and can start investigating them.

Are you loading too many bytes in the file for download?

Are you keeping too many references in session?

Once upon a time we had a similar problem and after several weeks we came to know that we were accumulating the context of the pages in the session so that all the visited pages were kept in memory all the time. But once we corrected it, the problem was solved.

Comments

Popular posts from this blog

mysql - BLOB/TEXT column 'value' used in key specification without a key length -

c# - Using Vici cool Storage with monodroid -

python - referencing a variable in another function? -