By the way, your comment about the higher traffic site having more problems also supports that it may be a memory threshold that is causing this.

---

It's very interesting to think that in ten minutes my site would generate so much memory as to trip the logout.

I've been getting strong hints they want my site off their host so I bet this is what is going on.  But I can't think of how/why my site would use so much memory.  And actually since I've gotten rid of the DNN search/results modules they've said my memory has been acceptable.

Of course they may have limited it too...which would make it acceptable.

I need to find a way to monitor my site's memory usage so I can see what's actually going on and if/why it's using more memory.

It'll be great if this is the reason and I've been jumping through hoops and my code to figure out a problem that isn't even there because they set something without telling me.

Last I heard my site is doing fine but I'll email them and figure it out.  Thanks for the help.

---

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

Last they told me...the site was using about 114MB.  When it was spiking it was using 295MB but that issue has been solved.

The funny thing is they didn't even notice the issue.  I sent them an email telling them about the memory error I was getting and they said my site looked normal and if it didn't happen too frequently to just not worry about it.  Months later I persisted and then they offered the isolated app pool, I took it, and they determined I had an issue.  I got it resolved but I'm really not sure what is set on the server.

---

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