Re: KB 812012 - WebClass memory leak
From: Steve Edwards (steve_online_at_microsoft.online.com)
Date: 03/25/04
- Previous message: Jim Deutch: "Re: VB6 + Access97 + DAO corruption"
- In reply to: Simon Wadsworth: "KB 812012 - WebClass memory leak"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 25 Mar 2004 14:18:12 -0600
Hi Simon,
Basically this problem occurs when the component is run within a
Webclass and you call the Split function frequently. For example running an
application that calls split frequently (10 threads against 12 pages), over
a long period of time (24 hours). We identified the leak was coming from
the VB runtime as a result of calling VirtualAlloc during the call to Split,
but only from within a WebClass component. As a result of the bug, the
small block heap would keep growing by 64k increments. The hotfix you
mention in 812012 addresses this leak.
Note: you can workaround this bug by using Split inside a VB dll and host
the package inside COM+, i.e., moving the calls to Split out of the WebClass
dll.
Thanks,
Steve Edwards - VBCPR
"Simon Wadsworth" <simon.wadsworth@logicacmg.com> wrote in message
news:79BD144F-5FF6-4729-910C-DF3BC4D5E2B0@microsoft.com...
> I have found KB 812012 which warns of a memory leak which may occur when
using Split() inside a WebClass. There is little detail in the article.
>
> I would like to know under what circumstances the leak occurs so that I
can analyse our code for issues. We do use Split() in our WebClasses so this
may affect us.
>
> I already contacted PSS as suggested in the article but got a useless
reply asking me to contact PSS!
>
> Thanks
> Simon
- Previous message: Jim Deutch: "Re: VB6 + Access97 + DAO corruption"
- In reply to: Simon Wadsworth: "KB 812012 - WebClass memory leak"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|