| |
I was helping a colleague out with an OOM (OutOfMemory) situation he was dealing with. Problem description: Their applications memory usage would grow over time until they finally ended up with an out [read more]
|
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 [read more]
|
his is an issue I come across once in a while and since I am not a COM expert by any means I actually had to check in with our COM guys to see what was going on in this case, and as it turned out (thi [read more]
|
|
Randomly when browsing the application we get the "Internet Explorer cannot display the webpage" page, and the following event is found in the system eventlog ...
|
When you use authenticode signed assemblies in an application, the application needs to go out and check the certificate revocation lists (CRLs) to verify that the signature is still valid the first t [read more]
|
Issues caused by frequent application restarts are pretty common. If you are interested in what causes application restarts in general, and how you can monitor application restarts and what causes the [read more]
|
|
ASP.NET Memory: Thou shalt not store UI objects in cache or session scope
|
One of the synchronization methods in .NET is the ResetEvent. It comes in two flavors, the AutoResetEvent which resets itself immediately after it is set, and the ManualResetEvent which as the name s [read more]
|
Last week I was working with on a case where they were getting this error message HttpException (0x80004005): Validation of viewstate MAC failed. If this application is hosted by a Web Farm or clust [read more]
|
|
If you use mixed mode dlls (assemblies with .net and c++ code) you need to take care to not have any .net entry points so that you don't end up with a GC/LoaderLock deadlock.
|
After making some changes to their domains one of my customers noticed that their ASP.NET 2.0 applications didn't respond anymore. HTML pages and images were serving just fine as well as their ASP.NET [read more]
|
The situation we are facing is that the ASP.NET process starts to go hey wire both in response times and in memory usage. All of a sudden memory just starts growing and growing and we need to figure [read more]
|
|
Lately, no matter where you turn there are LINQ presentations and Silverlight demos. A couple of years back the hot new stuff was webservices and XML.
|
If you were to compare the taste of the oranges in the fruit basket at work to the taste of the apples you bought on your way home and realize that they taste differently, what would your conclusion a [read more]
|
We have seen a few cases lately where ASP.NET apps die due to an unhandled CryptographicException when finalizing a SafeHandle. Here is the explanation of why this happens and what you can do to avoid [read more]
|
When you debug asp.net applications it is often useful to find out which requests are currently executing, how long they have been executing, what the querystring was etc. Since getting this informati [read more]
|
|
Since one of the most common memory issues I encounter is too much cache or session state I figured that showing you how to retrieve session data would be good.
|
By default when you run IIS on a 64-bit machine you will still be running a 32-bit w3wp.exe, so apart from a few differences, like being able to use 4 GB virtual bytes instead of 2 GB virtual bytes th [read more]
|
Recently we have been getting quite a few similar hangs in ASP.NET. From the first look they really aren't all that similar but when we get down to the nitty-gritty we see that they all hang or rather [read more]
|
This is a bit of a continuation of ASP.NET Memory Issue: High memory usage in a 64bit w3wp.exe process so if you haven't checked it out you might want to just glance over it before reading this one to [read more]
|
A local radio show has started giving out cookie points to their interviewees for personal development, and the other day my coworker decided to give me one for debugging a perf issue in kernel-mode.. [read more]
|
|
Memory in our ASP.NET application (w3wp.exe) keeps growing and growing and requests become slower and slower as time goes by.
|
|
The scenario is a web site that constantly crashes within minutes or seconds of startup, and a dump has been taken on process shutdown (adplus -crash -pn w3wp.exe)
|
|
I get enough issues relating to bad perf caused by large viewstate that I felt like it is time to dedicate some blog space to it, so here is a typical problem description for this type of problem.
|
|
It's been a while again. Lots of prepping for the debugging workshops and a bit of re-modeling done to the house but now it's time to write again...
|
Last night I got a question from one of the readers of the blog that went like this: “We are facing a problem that i cannot understand, every now and than i see that my app domain is recycled (i have [read more]
|
Rather than spending a lot of time on explaining the details of the garbage collector, I'll refer you to Maoni's blog for some very interesting reading, but in this case study I want to show you how t [read more]
|
|
Recently my colleague Doug wrote a nice post on Nine tips for a healthy "in production" ASP.NET application.
|
|
Wherever possible strong name and install to the global assembly cache (GAC) any assemblies that are used by more than one ASP.NET application. This will reduce memory consumption.
|
|
In ASP.NET 1.1, do not deploy strong named assemblies to the BIN directory (i.e. if they are strong named make sure you DO put them in the GAC).
|
|