I never did verify but my conclusion is that either the DNN3.2.2 Search Input or Search Results module was causing the problem.

I reached that conclusion by disabling all modules on my homepage and replacing them one by one.  The last two were the search modules.  I didn't replace them so see if the error came back and verify but I suspect them.  I haven't gotten the memory error since.

---

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

My logs show a bunch of these errors. Gets bad enough that the server stops responding for a while. I did not have the problem at all until I upgraded to 4.3.5, but I suspect that it's a 3rd party module, not 4.3.5 thats the problem. I have 4.3.5 installed on another server and it's be running perfect since it's release, no errors in the event logs at all.

I have seen the posts about the Events module, and this could be the problem since I started using it about the same time as the upgrade to 4.3.5.

I'm gonna go through and disable the search on everything and see what happens.

---

Icthus Technologies

Building Faith on the Internet

Is there a generally accepted amount of memory that needs to be allocated to a DNN site's application pool?  Purplebox mentioned 100 or 150 MB.  I too once had these errors and my host increased the memory allocation and the issue went away.  But if your host has more than one DNN site in the same pool with yours, maybe that's the issue.  Perhaps they aren't taking into account the high DNN needs per site divided into the total allocated to your pool (assuming IIS 6.0)?  Is your host one that specializes in DNN?

In my case the page with the errors was using a customized repository module.

---

Shawn Duggan MCPD
BlueTango Software - Canada Web Content Management
Website Design | DotNetNuke Hosting | DotNetNuke Tips and Tricks Blog
AuthIntegrator - The Easy Way To Integrate DNN and ASP.NET Applications
KeepAlive - Why Should Your Site Be Slow?