TECHNOLOGIES
FORUMS
JOBS
BOOKS
EVENTS
INTERVIEWS
Live
MORE
LEARN
Training
CAREER
MEMBERS
VIDEOS
NEWS
BLOGS
Sign Up
Login
No unread comment.
View All Comments
No unread message.
View All Messages
No unread notification.
View All Notifications
Answers
Post
An Article
A Blog
A News
A Video
An EBook
An Interview Question
Ask Question
Forums
Monthly Leaders
Forum guidelines
have2do
NA
1
0
Get exception : System.OutOfMemoryException
Mar 17 2004 4:01 AM
Some background: I have this website running for about 6 months with Caching, with no problems. After done some changes, including expansion of the caching, I've been getting System.OutOfMemoryException exception. We are talking about a site with about 1000 visitors per day. Symptoms: The ASP Worker Process reaches about 950 mb use in task manager. After adding two more GB's of RAM to the server (4 GB total), it reaches a peak about 1120 MB and then trow the exception : System.OutOfMemoryException, with a lot of free system memory. When I get the exception, the only way to solve it is by killing the worker process thread, because the exception is killing all build .net web-sites. I've been searching my code through for deadlocks / infinite loops...with no result. Beside that, I've changed machine.config with following attribute in the processModel : memoryLimit="85" What I've come to is that this allows the ASP Worker Process to use the total amount of 85% system memory, before it releases some of the Cached Data. I have a suspect the cache for being the trouble-maker in this case. Mainly because every time I've received the exception, the worker process used about 1120 MB. It's a win2k server (newest SP), SQL Server 2000 and .NET Framework 1.1 I've searched google with no luck, hope one of you can help me out, I'm very desperate. Kind of unsatisfing solution, killing the worker process when I get the exception, and watching the server die for some minutes before the cache does it's thing. PS: It's not output caching, but httpContext.Cache object.
Reply
Answers (
0
)
SelectedIndexChanged
3 errors.. one line.. makes no sense to me...