From time to time we get issues with high memory and performance issues due to massive viewstate. I have talked about it before here , but I thought I'd show some techniques for finding out which pages have high viewstate. If you look at a memroy dump of your process in windbg and notice that your large object heap is riddled with viewstate strings, that doesn't really tell you much, except for that you have some pages that have high viewstate, so the goose chase begings trying to find the source of these viewstate strings... Btw, if the sentence above made no sense to you at all, you might want to check out the viewstate debugging article, to figure out how you identify that you have lots of large viewstate strings in the first place...(read more) ...
Go to the complete details ...