Page 1 of 1

Waiting for profiled process to start never finishes

Posted: Tue Mar 29, 2005 7:10 pm
by Darren Zwonitzer
I am using the most recent release version When I try to profile a VB.NET smart client application (.exe) I get the message "Waiting for profiled process to start." That message never goes away, even after my application has started and is awaiting input.

.NET framework 1.1 SP1

The startup object is a form that calls web services. The application seems to startup and operate just fine, I just can't profile the memory as the message never disappears.

What can I do to correct this?

Posted: Wed Mar 30, 2005 11:03 am
by Andreas Suurkuusk
There should be no problem to connect to a VB.NET application. Maybe the profiler is not registered correctly. I recommend that you try to reinstall the software and see if that helps.

If you still have a problem connecting to your application, you can help us solve the problem by enabling logging. To enable logging you must supply the "/log" command line argument to the profiler executable (NetMemProfiler.exe). This will create three log-files in the program directory: ProfilerLog.txt, ProfilerClientLog.txt and AssertLog.txt (AssertLog.txt will probably be empty). If you send these log files to, we will hopefully be able to find out why you fail to connect to your application.

Waiting for profiled process to start never finishes

Posted: Mon Jun 06, 2005 3:06 pm
by Thomas

Same problem here, i downloaded the trial version,

then launched my program
-i use Microsoft Visual C++ .NET
microsoft visual studio .net 2003 (MDE v7.1.3088
microsoft .Net framework 1.1 v1.1.4322 SP1

i tried to launched the memory profiler from .net and externaly, but same problem, the "waiting for process" dialog never finishes, and if i use the /log command argument, there isn't any log,

if i close my program, the dialog is still here.
if i press the cancel button, it offers me to close my program, but whatever i do, it does nothing.

is there something i missed ?

Thank you,

Posted: Mon Jun 06, 2005 8:53 pm
by Andreas Suurkuusk

The log-files are important to us in order to find out why you fail to start profiling your application. It's very strange that you don't get at least one log file (ProfilerClientLog.txt) when supplying the /log switch. Are you sure that you have write access to the installation folder of .NET Memory Profiler?

I suggest that you make a complete reinstall of the profiler and then try to create the log-files again.

1. Exit Visual Studio.NET and uninstall .NET Memory Profiler.
2. It seems like VS.NET sometimes makes shadow copies of some files so you also need to make sure that there is no left-over files from the previous installation. (e.g by searching your hard-drive for core profiler files, such as NetMemProfiler.exe, NetMemProfilerBase.dll and ProfilerCallback.dll).
3. Reinstall the software.
4. Run the command "<InstallDir>\NetMemProfiler.exe /log". This should create three log-files (after having profiled an application): ProfilerClientLog.txt, ProfilerLog.txt and AssertLog.txt (AssertLog.txt is normally empty).

If you manage to create the log files, please send them to