By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,929 Members | 1,447 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,929 IT Pros & Developers. It's quick & easy.

Debugging Memory leaks?

P: n/a
I'm posting this in anticipation for troubleshooting tomorrow,
however:

I have a project I just finished up that I'm beta testing now.

It's comprised of a main core Window Service, with multiple support
libraries I developed as PlugIns.

I know the Garbage Collector will handle and release memory as it
needs to (or something like that), but in the past 10 minutes or so
while watching the Task Manager I've watched the application spin from
a starting mem usage of 32,480 up to what is at the time of this
posting, 32,528K.

Whenever it increases, it does so in increments of 4K. It seems to be
hovering around 32,528 for the most part atm.

What I would like to know how to do is "monitor" memory usage for each
of the PlugIns (Window Class Libraries) that are running in
conjunction with the Core Test App (Windows Application) so I can:

1. Start the Test Application
2. View the memory Usage of each activated PlugIn + Core Test App
3. Monitor the memory usage of each PlugIn + Core Test App.

In hopes I can see which one (if any) is not releasing memory as I
would expect it to.

All PlugIns are developed in C#, Test App is written in C# as well.

Before I confuse anyone, I know I mentioned Windows Service above. I
created a Windows Application that calls a Core Window Class Library
that the Windows Service normally would call. And this Core Window
Class Library then spawns off/Disposes the Support PlugIns as needed.

Any feedback appreciated, and Happy Holidays.
Nov 15 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Hi Cider123,

I not sure this will help, but I have come accross the same problem when
using COM components inside my managed code. Check for static methods
calls, thats where my main problem was.

Hope this helps,

Marco
"Cider123" <ci******@hotmail.com> wrote in message
news:55**************************@posting.google.c om...
I'm posting this in anticipation for troubleshooting tomorrow,
however:

I have a project I just finished up that I'm beta testing now.

It's comprised of a main core Window Service, with multiple support
libraries I developed as PlugIns.

I know the Garbage Collector will handle and release memory as it
needs to (or something like that), but in the past 10 minutes or so
while watching the Task Manager I've watched the application spin from
a starting mem usage of 32,480 up to what is at the time of this
posting, 32,528K.

Whenever it increases, it does so in increments of 4K. It seems to be
hovering around 32,528 for the most part atm.

What I would like to know how to do is "monitor" memory usage for each
of the PlugIns (Window Class Libraries) that are running in
conjunction with the Core Test App (Windows Application) so I can:

1. Start the Test Application
2. View the memory Usage of each activated PlugIn + Core Test App
3. Monitor the memory usage of each PlugIn + Core Test App.

In hopes I can see which one (if any) is not releasing memory as I
would expect it to.

All PlugIns are developed in C#, Test App is written in C# as well.

Before I confuse anyone, I know I mentioned Windows Service above. I
created a Windows Application that calls a Core Window Class Library
that the Windows Service normally would call. And this Core Window
Class Library then spawns off/Disposes the Support PlugIns as needed.

Any feedback appreciated, and Happy Holidays.

Nov 15 '05 #2

P: n/a
Looks like I am ok. I remoted in late tonight and checked up on it.

When I was leaving work, the memory usage was back down to 32,480'sh.
Checking on it tonight, 32,560'sh.

So it looks like everything is releasing as it should be.

C# in .NET is da bomb!

I was just hoping to find a way to monitor memory usage while an
application was running, and active memory usage on each PlugIn that
might be active within that application.

I would think each PlugIn would be defined as a separate instance
somewhere that could be monitored, but not really sure. Just wishful
thinking.

It may very well be possible to do that, I just don't know how.
Nov 15 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.