Here\'s my environment: IIS7.5 on Win 7, .NET 4, App Pool Integrated
web.config
&l
I had a similar issue on my site. In my case I had a page that contained a number of grids that each called a asmx webservice to retrieve their data. If the user navigated away from the page before all of the web requests had completed, then that user's session could become very slow (at least a couple of minutes to load a page), but other users' sessions would be unaffected by the slowness. For me, the issue began when I installed .NET 4.5 on the server.
I found a page here: http://forums.asp.net/t/1888889.aspx/1?Question+regarding+a+possible+bug+within+NET+4+5 that talks about this being a known issue with .NET 4.5. The bug can be triggered if site is using integrated mode and the browser disconnects while waiting for a page that's using the ASP.NET session. (See post for more details).
I believe that your double-postback case might cause the browser to abandon one of the requests, so it seems like this would apply. In addition, I and others have noticed that the bug seems to be more commonly seen when using IE (although this is just a coincidence - it's not an IE bug)
The post also describes a workaround (adjusting the uploadReadAheadSize setting in the web.config), and that workaround solved the problem for me.