Comments
Sort by recent activity
The problem typically happens when aspnet_wp reaches around 700mb but it does that after the second reload of the frontpage, which makes it impossible to debug the website properly, normally it reaches 200-300 mb without running the profiler, so i'm guessing that a lot of debug info is injected into the process? / comments
The problem typically happens when aspnet_wp reaches around 700mb but it does that after the second reload of the frontpage, which makes it impossible to debug the website properly, normally it rea...