AtlTraceTool8 not working
We use AtlTraceTool8 of VS2005 to switch on certain trace info while debugging.
On my W7 x64, AtlTraceTool8 works only for a certain period of time, after that no application including itself is displayed anymore, and refreshing leads to a app crash.
For test I logged in freshly, started AtlTraceTool8 (which displayed itself as an valid application), and locked the PC over night. Next morning, after refreshing AtlTraceTool8 display, nothing is there anymore.
After logging out and in again, everything is fine.
Anybody able to explain that? It is really nasty, as we have created an own trace category, and I'm no longer seeing important debugging info.
On my W7 x64, AtlTraceTool8 works only for a certain period of time, after that no application including itself is displayed anymore, and refreshing leads to a app crash.
For test I logged in freshly, started AtlTraceTool8 (which displayed itself as an valid application), and locked the PC over night. Next morning, after refreshing AtlTraceTool8 display, nothing is there anymore.
After logging out and in again, everything is fine.
Anybody able to explain that? It is really nasty, as we have created an own trace category, and I'm no longer seeing important debugging info.
ASKER
That tool is going into the right direction. But my issue is not application-related at all. No application is running, no MSDEV, no release, only AtlTraceTool8, Outlook 2007 and different Internet Browsers.
Can you track memory and (resource) handle usage usage overnight along with just the trace tool working?
What you describe sounds like the behaviour from a resource leak (and makes me think the trace tool has a serious bug in it). <Or you have some virus app running on this machine - have you done a full virus scan?>
What you describe sounds like the behaviour from a resource leak (and makes me think the trace tool has a serious bug in it). <Or you have some virus app running on this machine - have you done a full virus scan?>
ASKER
I will try to do that ASAP, but have ongoing projects running over night, so it might last some time until I can prepare for it.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
http://msdn.microsoft.com/en-us/library/khbh432d(v=VS.80).aspx
If you suspect a memory leak in this tool, it makes sense to write a small test application that will do nothing but log. I don't think that this is a case.
Can you post a code that you use for the logging?
I think that the program itself has a memory or GDI leaks and that causes the crash. The most funny case, if the code used for the logging has a problem. You can test the app with a memory profiler / error detection - something like Bound Checker or Purify+.