Unable to launch a profiler (Performance or Allocationà
Hi, I can't use AQTIME since several weeks. When I start the profiler, the process stops and do nothing. I reinstalled AQTIME but the same problem remains. I have a log message saying: "Event Thread ID Time User breakpoint is at address 0xFFE009AB (module Unknown module) 11296 09:33:31:667" Can you help me? BR Minh-Huy
AQtime 8.20 and C++Builder XE5 not working
Hi, I have to profile a project within XE5 with AQtime 8.2 but whne I lounch the command "Run with profiler" it seems starting but it stop to do anithing after some second. The module attached does not starts the any profiled data were collected. Do you have some suggestion to fixing it? I tried to biuld my 32 bit project on Windows 10 64 bit and Windows 11 64 bit Thanks for attention GZ
what next
i have been hacked some times ago that disarranged and disorganized all my system so i need a single working space for myself only now, either in my device system or in my internet services in any other ways, also a strongroom protections for all my works and accounts and make it invisible and impossible for hackers and trackers from having access over my system no matter how greate the hacker system is, also make their command trigger back to them without touching my sytem.AQTimePro access violation when try new project
Hi, I'm just starting on it to test AQTimePro with Delphi XE7, but when I try to create a new project I'm getting an Access Violation error, I did some search about it but I did not find nothing, can you let me know if there is something that I can do to fix it ? I think the process is not working because of this error. Thanks.
ERangeError on program start up using the Performance Profiler in Delphi 10.1 Berlin
To improve the performance of our program, we've recently started to use AQtime Pro 8, but we're facing the following issues: After selecting all modules of our executable and running the program with profiling activated, we're getting a madExcept error message (see below) The error also occurs when disabling madExcept and doesn't occur when starting the program directly or in debug mode in Delphi. The instrumenting modules procedure doesn't return any errors. We can avoid the error, when excluding some of the program's units. Unfortunately, the units we have to exclude, are exactly the units we want to analyze. Following settings are active: Thread model: Win32 threads Active counter: Elapsed Time Profile <Root> routine NOT selected Disable inlining NOT selected Profile .NET runtime NOT selected Changing these settings never led to a working outcome, though. Error message: ERangeError call stack: main thread ($4064): 00416c5d +5d XXX.exe System 34247 +9 DynArraySetLength 0041705c +2c XXX.exe System 34384 +9 @DynArraySetLength thread $3e5c: 7fff9705 +0e KERNEL32.DLL BaseThreadInitThunk 7fff9719 +1b ntdll.dll RtlUserThreadStart thread $6804: 7fff9705 +0e KERNEL32.DLL BaseThreadInitThunk 7fff9719 +1b ntdll.dll RtlUserThreadStart thread $79c: 7fff9705 +0e KERNEL32.DLL BaseThreadInitThunk 7fff9719 +1b ntdll.dll RtlUserThreadStart thread $2588: 7fff9705 +0e KERNEL32.DLL BaseThreadInitThunk 7fff9719 +1b ntdll.dll RtlUserThreadStart thread $497c: 7fff9705 +0e KERNEL32.DLL BaseThreadInitThunk 7fff9719 +1b ntdll.dll RtlUserThreadStart thread $5f10: 7fff93f4 +f7 KERNELBASE.dll WaitForMultipleObjectsEx thread $3920: 7fff9705 +0e KERNEL32.DLL BaseThreadInitThunk 7fff9719 +1b ntdll.dll RtlUserThreadStart thread $5388: 7fff9705 +0e KERNEL32.DLL BaseThreadInitThunk 7fff9719 +1b ntdll.dll RtlUserThreadStart thread $5354: 7fff93f4 +f7 KERNELBASE.dll WaitForMultipleObjectsEx 7fff9705 +0e KERNEL32.DLL BaseThreadInitThunk 7fff9719 +1b ntdll.dll RtlUserThreadStart thread $5398: 7fff93f2 +8c KERNELBASE.dll WaitForSingleObjectEx 7fff9705 +0e KERNEL32.DLL BaseThreadInitThunk 7fff9719 +1b ntdll.dll RtlUserThreadStart thread $466c: <priority:2> 7fff93f4 +f7 KERNELBASE.dll WaitForMultipleObjectsEx 7fff9705 +0e KERNEL32.DLL BaseThreadInitThunk 7fff9719 +1b ntdll.dll RtlUserThreadStart thread $59d8: 7fff93f2 +9a KERNELBASE.dll SleepEx 7fff9705 +0e KERNEL32.DLL BaseThreadInitThunk 7fff9719 +1b ntdll.dll RtlUserThreadStart thread $56f4: 7fff93f2 +8c KERNELBASE.dll WaitForSingleObjectEx 7fff9705 +0e KERNEL32.DLL BaseThreadInitThunk 7fff9719 +1b ntdll.dll RtlUserThreadStart thread $457c: 7fff93f2 +8c KERNELBASE.dll WaitForSingleObjectEx 7fff9705 +0e KERNEL32.DLL BaseThreadInitThunk 7fff9719 +1b ntdll.dll RtlUserThreadStart thread $5954: 7fff93f2 +8c KERNELBASE.dll WaitForSingleObjectEx 7fff9705 +0e KERNEL32.DLL BaseThreadInitThunk 7fff9719 +1b ntdll.dll RtlUserThreadStart thread $5130: 7fff93f2 +8c KERNELBASE.dll WaitForSingleObjectEx 7fff9705 +0e KERNEL32.DLL BaseThreadInitThunk 7fff9719 +1b ntdll.dll RtlUserThreadStart thread $66e4: 7fff93f2 +8c KERNELBASE.dll WaitForSingleObjectEx 7fff9705 +0e KERNEL32.DLL BaseThreadInitThunk 7fff9719 +1b ntdll.dll RtlUserThreadStart thread $6920: 7fff93f2 +8c KERNELBASE.dll WaitForSingleObjectEx 7fff9705 +0e KERNEL32.DLL BaseThreadInitThunk 7fff9719 +1b ntdll.dll RtlUserThreadStart thread $686c: 7fff93f2 +8c KERNELBASE.dll WaitForSingleObjectEx 7fff9705 +0e KERNEL32.DLL BaseThreadInitThunk 7fff9719 +1b ntdll.dll RtlUserThreadStart thread $4818: 7fff93f2 +8c KERNELBASE.dll WaitForSingleObjectEx 7fff9705 +0e KERNEL32.DLL BaseThreadInitThunk 7fff9719 +1b ntdll.dll RtlUserThreadStart thread $2898: 7fff93f2 +8c KERNELBASE.dll WaitForSingleObjectEx 7fff9705 +0e KERNEL32.DLL BaseThreadInitThunk 7fff9719 +1b ntdll.dll RtlUserThreadStartDuplicate Routines entry/exit
I don't understand. Why can I not Start profiling when entering a function and Stop profiling when exiting the same function? I would think that this would be a very common thing to do. For that matter, why is there a limit of only one anyway? I can think of other use cases, such as where I'd want to stop and generate a report at the exiting of a function. What's up with this? Why the limitation?No source access with allocation profiler
Hey guys, I am experiencing problems accessing the source files in the editor's tab if I use the allocation profiler. Search paths are set up correctly since I can perfectly view the source (and the line per line analysis) if I use the performance profiler. As soon as I switch over to the allocation profiler no source is available. Of course the executable remains untouched, so it is the same for the two profiler runs. It's a Win32 Delphi Application. The configuration was done according to https://support.smartbear.com/viewarticle/54592/ I followed these two tutorials for the allocation profiling: https://support.smartbear.com/articles/aqtime/fixing-memory-leaks-with-aqtime/ and https://support.smartbear.com/viewarticle/43862/ I tried the troubleshooter but could not find a solution concerning my problem. It works perfectly with performance but not allocation profiler. Is there any kind of difference between them (concerning source code)? Thanks in advance, Alex
