[Help] why memory leakage during managed automation object creation / destruction ?

Question

0.00/5 (No votes)

See more:

VS2015

Hello Everyone,
I would like to share with you the following stranged issue:

How is it possible to have memory leakage just by creating and releasing an instance to an empty automation class ?
What is the magic behind ? Is there a leakage between managed and unmanaged inter-connection ?

Thank you very much in advance.
Best regards.
MiQi.

What I have tried:

Here is the test app package to test on your end:
Sample program package.
(I am using Visual Studio Pro 2015)

Posted 25-Aug-16 3:38am

SuperMiQi

Updated 25-Aug-16 4:12am

Patrice T

v3

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dave Kreskowiak · Answer 1 · 2016-08-25T03:44:00

Probably because you're looking in Task Manager for memory usage of a .NET app. Don't. It's lying to you.

Task Manager shows how much memory is RESERVED for your app, not how much it's actually using.

For better memory statistics, use PerfMon and the .NET Memory counters or a dedicated .NET memory profiling tool.