KB 911309: memory leak w/ application that has custom URL's

[Steve Besalke]

Greetings,

I have a question about KB 911309
(http://support.microsoft.com/?kbid=911309) and what it fixes. My company is
using a purchased ASP.NET application and virtual directories to provide
group access to the application. We are using Windows 2000 Server, IIS 5,
and .NET 1.1 SP1. Here is the scenario. The main virtual directory, App
points to e:\Program Files\App in IIS. Then we have virtual directories
Mirror1, Mirror2, etc. pointing to e:\Program Files\App as well. When the
main virtual directory, App, receives a request, aspnet_wp creates a
directory in "Temporary ASP.NET Files" for App, caches the dlls from
E:\Program Files\APP under the directory, and loads them into memory. When
Mirror1 and Mirror2 are requested, aspnet_wp creates temporary directories
for them as well and loads 2 more copies of the dll's into memory. When I
read KB 911309, it sounded to me like the fix would change the behavior so
that only one copy of the DLL's would be loaded into memory. However, I
think I am misread and/or misunderstood what kb 911309 fixes. Is it intended
to fix aspnet_wp so that only one copy of the DLL's loads in the scenario
above or did I misunderstand?

[bruce barker \(sqlwork.com\)]

you misread. the fix was having more then one url point to the same aspx
page in the same vdir (the bug caused the page to be compiled and loaded
more than once into the same appdomain) . as every vdir get its own
appdomain, a shared dll, is loaded in to each appdomain.

-- bruce (sqlwork.com)
"Steve Besalke" <St**********@discussions.microsoft.com> wrote in message
news:A9**********************************@microsof t.com...

Greetings,

I have a question about KB 911309
(http://support.microsoft.com/?kbid=911309) and what it fixes. My company
is
using a purchased ASP.NET application and virtual directories to provide
group access to the application. We are using Windows 2000 Server, IIS 5,
and .NET 1.1 SP1. Here is the scenario. The main virtual directory, App
points to e:\Program Files\App in IIS. Then we have virtual directories
Mirror1, Mirror2, etc. pointing to e:\Program Files\App as well. When the
main virtual directory, App, receives a request, aspnet_wp creates a
directory in "Temporary ASP.NET Files" for App, caches the dlls from
E:\Program Files\APP under the directory, and loads them into memory.
When
Mirror1 and Mirror2 are requested, aspnet_wp creates temporary directories
for them as well and loads 2 more copies of the dll's into memory. When I
read KB 911309, it sounded to me like the fix would change the behavior so
that only one copy of the DLL's would be loaded into memory. However, I
think I am misread and/or misunderstood what kb 911309 fixes. Is it
intended
to fix aspnet_wp so that only one copy of the DLL's loads in the scenario
above or did I misunderstand?