After changing the timeout did you have to wait for an hour before the error occurred? If no, then it seems that the setting doesn't affect the timeout. Can you please try once more with checked Filter .NET Framework internals
and Ignore transitions options:
If profiling fails again, please send us feedback
from withing JustTrace. Just make sure that the Attach log files
option is checked. This will help us better analyze what might have gone wrong!
You mentioned that you are profiling on a virtual machine. Besides being slower, profiling on a VM can generate somewhat misleading performance data, so I would recommend you to profile on a real machine, if possible.
Looking forward to your response!
DevCraft Q1'14 is here! Join the free online conference to see how this release solves your top-5 .NET challenges. Reserve your seat now!