BUG: memory leak in mscordbi.dll

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Hanno Lewandowski - 10 Dec 2003 09:29 GMT

Only for pedants :
I dicovered a memory leak in the
interface ICorPublish (mscordbi.dll)

ICorPublish::GetProcess(DWORD id, ICorPublishProcess** p)

Every time this function is called, it lose
8 bytes of virtual memory

Reply to this Message

Nick Hertl - 16 Dec 2003 18:34 GMT

Not that I know tons about C++ programming, but wouldn't that actually be
expected? I mean... you have a pointer as an out parameter, and the
function needs to alocate space for the new ICorPublishProcess** p that its
going to send you. I would actually expect you to lose 8 bytes of memory
every time you call this function, but correct me if I'm wrong about this.

----------------
This posting is provided "AS IS" with no warranties, and
confers no rights.

Please do not send e-mail directly to this alias. This
alias is for newsgroup purposes only.

Thanks
Nick

--------------------

>Content-Class: urn:content-classes:message
>From: "Hanno Lewandowski" <anonymous@discussions.microsoft.com>
[quoted text clipped - 24 lines]
>Every time this function is called, it lose
>8 bytes of virtual memory

Reply to this Message

Peter Koen - 16 Dec 2003 23:10 GMT

> Not that I know tons about C++ programming, but wouldn't that actually
> be expected? I mean... you have a pointer as an out parameter, and
> the function needs to alocate space for the new ICorPublishProcess** p
> that its going to send you. I would actually expect you to lose 8
> bytes of memory every time you call this function, but correct me if
> I'm wrong about this.

No, in C++ the memory for the pointer should be already there, it's just
passed by a **. At least if this is a simple COM call to an
Interfaceaquisition.

So if done right, this function shouldn't alter the amount of memory used
when returned.

greets
Peter

Signature

------ooo---OOO---ooo------

Peter Koen - www.kema.at
MCAD MCDBA
CAI/RS CASE/RS IAT

------ooo---OOO---ooo------

Reply to this Message

Jan Stranik - 19 Dec 2003 23:30 GMT

Hello Peter,
I'm confirming that there is a memory leak in the GetProcess method in
cases when the method is called with invalid PID. Thank you for reporting
this code defect to Microsoft. We will fix the leak in the future versions
of .NET runtime.

Regards
Jan Stranik

--------------------

| Subject: RE: BUG: memory leak in mscordbi.dll
| From: Peter Koen <koen-newsreply&snusnu.at>
| References: <0a5b01c3bf00$28757f40$a101280a@phx.gbl>

<lljXxMAxDHA.480@cpmsftngxa07.phx.gbl>

| Organization: Koen Electronic Media Agency
| User-Agent: Xnews/5.04.25
| Message-ID: <efI#JnCxDHA.1364@tk2msftngp13.phx.gbl>
| Newsgroups: microsoft.public.dotnet.framework.clr
| Date: Tue, 16 Dec 2003 15:10:24 -0800
| NNTP-Posting-Host: ist.doch.alles.nur.belangloses.blablabla.at

212.24.113.98

| Lines: 1
| Path:

cpmsftngxa07.phx.gbl!cpmsftngxa06.phx.gbl!cpmsftngxa09.phx.gbl!TK2MSFTNGP08.
phx.gbl!tk2msftngp13.phx.gbl

| Xref: cpmsftngxa07.phx.gbl microsoft.public.dotnet.framework.clr:9003
| X-Tomcat-NG: microsoft.public.dotnet.framework.clr
[quoted text clipped - 15 lines]
| greets
| Peter

Reply to this Message

Rate this thread:

BUG: memory leak in mscordbi.dll

Free Magazines