We are building a new experience for our SmartBear Community.
This site is now read-only. You can still browse and search as usual. Learn More
This site is now read-only. You can still browse and search as usual. Learn More
Forum Discussion
Profiled application runs slowly & AQTime unable to grab results
Hello,
I just downloaded AQTime Standard Edition version 7.30.537.647, and I am attempting to do a performance profiling of a .NET 4.0 application in C# created using Visual Studio 2010 professional. I am using the x64 version of AQTime, even though the profiled application is being built in x86.
My computer is an Intel Core i7 running Windows 7 64 bits, and has 8 GB of memory. Virtual memory is disabled.
The application I am attempting to profile consists of a console application and a DLL (both created in C#). I am adding both of these into the AQTime project. The projects were built according to the AQTime help instructions on how they should be built (in Debug mode and so on)
When I start the performance profiling, I choose the following settings:
- Thead Model: CLR-threads
- Active Counter: Ellapsed time
None of the checkboxes are enabled (profile <Root> runtime, disable inlining, Profile .net runtime)
After I start profiling, the console application starts, but it seems to be running really slowly. When I run the application compiled from Visual Studio or directly from the EXE file in Windows explorer, it takes around 52 seconds to finish. When I run it with the performance profiler, it never finishes even after 1 hour.
If while this slow profiling is taking place, I click the "Get results now" button in AQTime, a dialog box saying "AQTime is trying to obtain results from the application. Please wait...", appears, but it never goes away unless I click "Cancel". If I just click the "Terminate" button in AQTime, it doesn't grab any results either.
I tried AQTime with other .NET application I created, and it seems to work fine with those. This is the only one I am having problems with. My only wild guess is that this application uses multithreading synchronization using Monitor.Wait() and Monitor.Pulse() instructions. Please let me know if AQTime has some issue with using those.
At the end of this post I am including a dump of my AQTime event window.
Thanks in advance for your help with this issue.
Event Thread ID Time
Project run selected, current profiler is Performance Profiler. 23:16:11:107
Process create ID: 5176, Thread ID: 5452, Base address: 0x000D0000 5452 23:16:11:126
Module loaded: C:\Users\...\Documents\Visual Studio 2010\Projects\EvolutionChamber\EvolutionChamberConsole\bin\Debug\EvolutionChamberConsole.exe; Base address: 0x000D0000 File Size: 5632 Version: 1.0.0.0 5452 23:16:11:129
Module loaded: C:\Windows\SysWOW64\ntdll.dll; Base address: 0x77290000 File Size: 1293120 Version: 6.1.7600.16695 5452 23:16:11:134
Module loaded: C:\Windows\SysWOW64\mscoree.dll; Base address: 0x69230000 File Size: 297808 Version: 4.0.31106.0 5452 23:16:11:166
Module loaded: C:\Windows\SysWOW64\kernel32.dll; Base address: 0x768D0000 File Size: 1048576 Version: 6.1.7600.16850 5452 23:16:11:175
Module loaded: C:\Windows\SysWOW64\KernelBase.dll; Base address: 0x76400000 File Size: 272384 Version: 6.1.7600.16850 5452 23:16:11:179
Module loaded: C:\Program Files (x86)\SmartBear\AQtime 7\Bin\Extensions\aqNatProf.dll; Base address: 0x30800000 File Size: 1536048 Version: 7.30.537.86 5452 23:16:11:238
Module loaded: C:\Windows\SysWOW64\version.dll; Base address: 0x74830000 File Size: 21504 Version: 6.1.7600.16385 5452 23:16:11:321
Module loaded: C:\Windows\SysWOW64\msvcrt.dll; Base address: 0x765C0000 File Size: 690688 Version: 7.0.7600.16385 5452 23:16:11:374
Module loaded: C:\Windows\SysWOW64\user32.dll; Base address: 0x74DA0000 File Size: 833024 Version: 6.1.7600.16385 5452 23:16:11:621
Module loaded: C:\Windows\SysWOW64\gdi32.dll; Base address: 0x766F0000 File Size: 310784 Version: 6.1.7600.16385 5452 23:16:11:634
Module loaded: C:\Windows\SysWOW64\lpk.dll; Base address: 0x76670000 File Size: 25600 Version: 6.1.7600.16385 5452 23:16:11:642
Module loaded: C:\Windows\SysWOW64\usp10.dll; Base address: 0x764F0000 File Size: 627200 Version: 1.626.7600.16385 5452 23:16:11:645
Module loaded: C:\Windows\SysWOW64\advapi32.dll; Base address: 0x74D00000 File Size: 640000 Version: 6.1.7600.16385 5452 23:16:11:647
Module loaded: C:\Windows\SysWOW64\sechost.dll; Base address: 0x768B0000 File Size: 92160 Version: 6.1.7600.16385 5452 23:16:11:651
Module loaded: C:\Windows\SysWOW64\rpcrt4.dll; Base address: 0x75FE0000 File Size: 662528 Version: 6.1.7600.16385 5452 23:16:11:653
Module loaded: C:\Windows\SysWOW64\sspicli.dll; Base address: 0x74990000 File Size: 96768 Version: 6.1.7600.16484 5452 23:16:11:654
Module loaded: C:\Windows\SysWOW64\cryptbase.dll; Base address: 0x74980000 File Size: 36864 Version: 6.1.7600.16385 5452 23:16:11:656
Module loaded: C:\Windows\SysWOW64\shell32.dll; Base address: 0x74FC0000 File Size: 12867584 Version: 6.1.7600.16644 5452 23:16:11:658
Module loaded: C:\Windows\SysWOW64\shlwapi.dll; Base address: 0x75F80000 File Size: 350208 Version: 6.1.7600.16385 5452 23:16:11:659
Module loaded: C:\Windows\SysWOW64\ole32.dll; Base address: 0x75DC0000 File Size: 1413632 Version: 6.1.7600.16624 5452 23:16:11:661
Module loaded: C:\Windows\SysWOW64\oleaut32.dll; Base address: 0x762F0000 File Size: 571904 Version: 6.1.7600.16722 5452 23:16:11:663
Module loaded: C:\Windows\SysWOW64\imm32.dll; Base address: 0x75F20000 File Size: 119808 Version: 6.1.7600.16385 5452 23:16:11:670
Module loaded: C:\Windows\SysWOW64\msctf.dll; Base address: 0x74C30000 File Size: 828928 Version: 6.1.7600.16385 5452 23:16:11:672
Module loaded: C:\Windows\SysWOW64\winsta.dll; Base address: 0x72690000 File Size: 156160 Version: 6.1.7600.16385 5452 23:16:11:678
Module loaded: C:\Windows\SysWOW64\utildll.dll; Base address: 0x5FAA0000 File Size: 31744 Version: 6.1.7600.16385 5452 23:16:11:681
Module loaded: C:\Windows\SysWOW64\setupapi.dll; Base address: 0x74A90000 File Size: 1668608 Version: 6.1.7600.16385 5452 23:16:11:683
Module loaded: C:\Windows\SysWOW64\cfgmgr32.dll; Base address: 0x766C0000 File Size: 145920 Version: 6.1.7600.16820 5452 23:16:11:685
Module loaded: C:\Windows\SysWOW64\devobj.dll; Base address: 0x75C10000 File Size: 64512 Version: 6.1.7600.16820 5452 23:16:11:686
Module loaded: C:\Windows\SysWOW64\netapi32.dll; Base address: 0x72670000 File Size: 56832 Version: 6.1.7600.16385 5452 23:16:11:689
Module loaded: C:\Windows\SysWOW64\netutils.dll; Base address: 0x72660000 File Size: 22016 Version: 6.1.7600.16385 5452 23:16:11:691
Module loaded: C:\Windows\SysWOW64\srvcli.dll; Base address: 0x72640000 File Size: 90112 Version: 6.1.7600.16385 5452 23:16:11:694
Module loaded: C:\Windows\SysWOW64\wkscli.dll; Base address: 0x743A0000 File Size: 47104 Version: 6.1.7600.16385 5452 23:16:11:696
Module loaded: C:\Windows\SysWOW64\logoncli.dll; Base address: 0x5A960000 File Size: 127488 Version: 6.1.7600.16385 5452 23:16:11:699
Module loaded: C:\Windows\SysWOW64\browcli.dll; Base address: 0x5FBB0000 File Size: 41472 Version: 6.1.7600.16385 5452 23:16:11:702
Module loaded: C:\Windows\SysWOW64\samcli.dll; Base address: 0x70C30000 File Size: 50688 Version: 6.1.7600.16385 5452 23:16:11:704
Module loaded: C:\Program Files (x86)\SmartBear\AQtime 7\Bin\aqProf.dll; Base address: 0x10000000 File Size: 828464 Version: 7.30.537.0 5452 23:16:11:769
Module loaded: C:\Program Files (x86)\SmartBear\AQtime 7\Bin\aqComm.dll; Base address: 0x30200000 File Size: 189488 Version: 7.30.537.0 5452 23:16:11:774
Module loaded: C:\Windows\SysWOW64\ws2_32.dll; Base address: 0x76680000 File Size: 206336 Version: 6.1.7600.16385 5452 23:16:11:776
Module loaded: C:\Windows\SysWOW64\nsi.dll; Base address: 0x76450000 File Size: 8704 Version: 6.1.7600.16385 5452 23:16:11:778
Module loaded: C:\Windows\SysWOW64\RpcRtRemote.dll; Base address: 0x73E40000 File Size: 45568 Version: 6.1.7600.16385 5452 23:16:11:782
Thread create ID: 4100; Priority: Normal 4100 23:16:11:783
Thread create ID: 4324; Priority: Normal 4324 23:16:11:785
Module loaded: C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll; Base address: 0x68CA0000 File Size: 413520 Version: 4.0.30319.237 5452 23:16:11:820
Module loaded: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll; Base address: 0x67BE0000 File Size: 6735176 Version: 4.0.30319.237 5452 23:16:11:823
Module loaded: C:\Windows\SysWOW64\msvcr100_clr0400.dll; Base address: 0x67B20000 File Size: 771424 Version: 10.0.30319.1 5452 23:16:11:826
Thread create ID: 936; Priority: Normal 936 23:16:11:831
Thread create ID: 5796; Priority: Normal 5796 23:16:11:832
Module loaded: C:\Program Files (x86)\SmartBear\AQtime 7\Bin\Extensions\aqClrProf.dll; Base address: 0x02330000 File Size: 443440 Version: 7.30.537.86 5452 23:16:11:835
Module loaded: C:\Windows\SysWOW64\psapi.dll; Base address: 0x749F0000 File Size: 6144 Version: 6.1.7600.16385 5452 23:16:11:837
Module loaded: C:\Program Files (x86)\SmartBear\AQtime 7\Bin\msdia90.dll; Base address: 0x54260000 File Size: 666672 Version: 9.0.21022.8 5452 23:16:11:841
Module loaded: C:\Program Files (x86)\SmartBear\AQtime 7\Bin\aqProf.dll; Base address: 0x03030000 File Size: 828464 Version: 7.30.537.0 5452 23:16:11:844
Module unloaded: C:\PROGRAM FILES (X86)\SMARTBEAR\AQTIME 7\BIN\AQPROF.DLL; Base address: 0x03030000 5452 23:16:11:844
Thread create ID: 4376; Priority: Normal 4376 23:16:11:847
Thread create ID: 6132; Priority: Normal 6132 23:16:11:847
Thread create ID: 6000; Priority: Normal 6000 23:16:11:873
Application domain created: DefaultDomain 23:16:11:874
Module loaded: C:\Windows\assembly\NativeImages_v4.0.30319_32\mscorlib\93e7df09dacd5fef442cc22d28efec83\mscorlib.ni.dll; Base address: 0x66D50000 File Size: 14407680 Version: 4.0.30319.237 5452 23:16:11:903
Assembly loaded: mscorlib in the application domain DefaultDomain 23:16:11:929
Module loaded: C:\Windows\Microsoft.Net\assembly\GAC_32\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dll in the assembly mscorlib 23:16:11:954
Module loaded: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clrjit.dll; Base address: 0x625A0000 File Size: 385864 Version: 4.0.30319.237 5452 23:16:11:983
Module loaded: C:\Windows\Microsoft.NET\Framework\v4.0.30319\nlssorting.dll; Base address: 0x69210000 File Size: 56656 Version: 4.0.30319.237 5452 23:16:12:008
Assembly loaded: EvolutionChamberConsole in the application domain DefaultDomain 23:16:12:037
Module loaded: C:\Users\...\Documents\Visual Studio 2010\Projects\EvolutionChamber\EvolutionChamberConsole\bin\Debug\EvolutionChamberConsole.exe in the assembly EvolutionChamberConsole 23:16:12:061
Module loaded: C:\Windows\assembly\NativeImages_v4.0.30319_32\System\ffc825af968e2afbdd0d894b475331f3\System.ni.dll; Base address: 0x664A0000 File Size: 9086464 Version: 4.0.30319.236 5452 23:16:12:119
Assembly loaded: System in the application domain EvolutionChamberConsole.exe 23:16:12:121
Module loaded: C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System\v4.0_4.0.0.0__b77a5c561934e089\System.dll in the assembly System 23:16:12:146
Module loaded: C:\Users\...\Documents\Visual Studio 2010\Projects\EvolutionChamber\EvolutionChamberConsole\bin\Debug\EvolutionChamber.dll; Base address: 0x59F30000 File Size: 51712 Version: 1.0.0.0 5452 23:16:12:176
Module loaded: C:\Users\...\Documents\Visual Studio 2010\Projects\EvolutionChamber\EvolutionChamberConsole\bin\Debug\EvolutionChamber.dll; Base address: 0x023F0000 File Size: 51712 Version: 1.0.0.0 5452 23:16:12:180
Module unloaded: C:\USERS\...\DOCUMENTS\VISUAL STUDIO 2010\PROJECTS\EVOLUTIONCHAMBER\EVOLUTIONCHAMBERCONSOLE\BIN\DEBUG\EVOLUTIONCHAMBER.DLL; Base address: 0x59F30000 5452 23:16:12:180
Assembly loaded: EvolutionChamber in the application domain EvolutionChamberConsole.exe 23:16:12:181
Module loaded: C:\Users\...\Documents\Visual Studio 2010\Projects\EvolutionChamber\EvolutionChamberConsole\bin\Debug\EvolutionChamber.dll in the assembly EvolutionChamber 23:16:12:206
Module loaded: C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Core\2721a63758cab451543e8a58dc4ffeeb\System.Core.ni.dll; Base address: 0x64FB0000 File Size: 7069696 Version: 4.0.30319.233 5452 23:16:12:241
Assembly loaded: System.Core in the application domain EvolutionChamberConsole.exe 23:16:12:243
Module loaded: C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Core\v4.0_4.0.0.0__b77a5c561934e089\System.Core.dll in the assembly System.Core 23:16:12:274
Thread create ID: 4076; Priority: Normal 4076 23:16:12:346
4 Replies
Hi Andres,
Thanks for the detailed information. We really appreciate it.
this application uses multithreading synchronization using Monitor.Wait() and Monitor.Pulse() instructions. Please let me know if AQTime has some issue with using those.
We have no such information, so it's hard to say for sure that the problem is caused by these methods.To solve the problem, please try using the http://smartbear.com/support/troubleshooter/?prod=AQtime on our web site. Does it help?
One more suggestion: try using the AQtime Pro version to reproduce the behavior. For example, you can http://smartbear.com/products/development-tools/performance-profiling/sign-up/ from our web site and profile your application with it. Does the problem remain?
BTW, to help us investigate the problem and find a solution faster, please post here a sample application that we can use to reproduce the behavior.
Thanks.
- Hi Irina,
Thank you for your suggestions. Let me tell you my experiences attempting each of them:
- I tried to use the AQTime Troubleshooter, but after it asked me two questions it asked me to send a report to the support team. Since I only have the Standard version, it didn't let me send the report to the support team.
- I tried to reproduce the problem in AQTime Pro, but was unable to. AQTime Pro forced me to uninstall the Standard version, but after I finally installed the Pro one, I didn't find any way to get the trial key. I must have missed it somewhere, because it kept sending me to a page in the smartbear website where I was supposed to login with some Customer ID I don't have.
- Finally I attempted to create a more simple application where the problem could be reproduced, but after re-installing AQTime Standard, the problem was gone. After some investigation I found out that if I changed the compilation of my application to 64bits, AQTime could properly profile it. I don't really know why, since other .NET applications I have in 32 bits are profiled normally.
Anyway, my problem is solved, so thank you once again. - Hi I am stuck in the same situation, where AQ Time shows the message "AQ Time is trying to obtain the results from the profiled application. Please wait..." and it never completes.
My application is compiled for 32 bit, does AQ Time profiles only for 64 bit applications?
Please suggest, if it works for 32 bit compiled applications.
Thanks
Gaurav - TanyaYatskovska
Alumni
Hi Gaurav,
Profiling of 64-bit applications has some specifics. Please read the http://support.smartbear.com/viewarticle/43583/ article for more information. If this information doesn't help, I recommend that you go through the http://support.smartbear.com/troubleshooter/?prod=AQtime-8 to solve the issue or contact the AQtime Support Team (depending on your situation).
