I'm having this issue with the error being thrown on my site on a regular basis.  It seems quite a few people are.  Heck, if you Google the error you'll see a bunch of webpages cached with it and even see Nina's skinning forums have been cached with the error.

I've also seen a bunch of "it could be" guesses pointing to various culprits but haven't seen any hard evidence of where the problem lies.  My host says it's not their server.

I've seen articles saying it could be the SQL Server settings (http://dnnblog.venexus.com/Out+Of+Memory+Exception+On+Large+DotNetNuke+Website.aspx)

There are a couple threads suspecting it's the DNN Search indexing that is causing the problem.

Some say it's related to the loading up of the cache for a page.  This seems to make sense in my situation because logging in as admin gets rid of the problem (and I assume admin gets the real content not just what is cached).

This post says it's an issue with Windows Server 2003 SP1 (http://forums.asp.net/thread/1150765.aspx)

Anybody know what the real deal is?  In my situation, the error is only recieved on my homepage.  No other page.  So, I'm going to tinker with the modules on that page to see if I can isolate it.

I also wonder about "cache settings".  Right now they're set to "moderate caching" but I'm wondering if "heavy caching" will do anything positive.  Any ideas? 

I've extended my searchindexer to make it happen less frequently although I don't have enough data to know if it is the culprit.

Here is the error I'm recieving:

AssemblyVersion: -1
Method:
FileName:
FileLineNumber: -1
FileColumnNumber: -1
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
AbsoluteURL:
AbsoluteURLReferrer:
ExceptionGUID:
DefaultDataProvider:
InnerException: Exception of type System.OutOfMemoryException was thrown.
Message: DotNetNuke.Services.Exceptions.PageLoadException: Exception of type

System.OutOfMemoryException was thrown. ---> System.OutOfMemoryException: Exception of

type System.OutOfMemoryException was thrown. --- End of inner exception stack trace

---
StackTrace:
Source:
Server Name: Mine

---

I'm too poor for anything other than the community version

How much memory load are we talking about here?

DNN in it's own application pool uses lots of memory. it loads almost all .NET dll's sindce it uses all technology supported by .NET. I consider 100 megs as normal on a non caching DNN site. 150 megs when an admin logs in and does alot of admin stuff.

the article you link to talks about 500.000 pages? if they all cache 1K thats 500 megs of cache. 1K is easier to reach then you think, and then we aren't even counting the cache for the subsystem. (reflection cache, membership + profiel data, ...)

SQL server uses lot's of RAM but it seems to be verry friendly in giving it back to the system for other software, there is latency offcoarse

 

My experience says, an opteron with a whole lot of memory as a dedicated webserver is alot cheaper then a quad itanium to make up for not caching. so I put my large DNN projects on dedicated servers with 4 gigs of ram and the caching set as high as possible. (a day for static modules, heavy caching and custom modules cache *everything* that comes from the DB)

going dedicated might be worth the investment, at the verry least you will have acces to the eventlog + WMI to monitor DNN behavior yourself

---

Edit your Skin.xml and Container.xml files with:
Yannick's SXE

Are you using any 3rd party modules that could be causing the problem?