Search code examples
.netmemory-leaksgarbage-collectionmixedaqtime

AQTime: "Force Garbage Collection" button grayed out

I googled around a bit, but couldn't find a reason. My app is mixed (C#, VB.NET, C++/CLI and native C++). AQTime claims to be able to profile this kind of application, that's why I chose it.

It does profile OK, but it would be nice to be able to force Garbage Collection to rule out objects which are garbage but haven't been collected yet from the suspicious set.

I'm running the Allocation Profiler over an area of my code (some dlls), with these settings:

  • Check system memory Allocations: checked (all other unchecked)
  • Collect Stack information: None
  • Thread Model: CLR threads (I figured this would be necessary since the GC handles managed threads, doesn't it?)

AQTime version is 6.50.498, running on Windows XP Professional SP3

Is it possible to use the "Force Garbage Collection" feature in this scenario? If so, how do I configure AQTime?

Solution

  • There is a known problem with calling Garbage Collection from AQtime when profiling .NET Framework 4 applications - this function does not work for applications running under this version of .NET Framework. For earlier .NET Framework versions, this should work just fine.

    There is no solution to the problem so far, but the investigation is going to be continued soon.

    --

    Alex