Changing Processor Affinity Looses Profiling Session

[ticktock]

v3.0 preview release 2, changing processor affinity from cpu 0,1,2,4 to cpu 0 resulted in the loss of the profiling session on a asp.net webservices application running in aspnet_ws.exe .net v1.1.

This behaviour is not experienced on v2.6.

[Andreas Suurkuusk]

Hi,

Thank you for the information. This is something we have not tested, but we will make sure that we look into this before making the next release of .NET Memory Profiler 3.0.

What settings were you using when this problem occured? Was the unmanaged resources tracker enabled?