h_hasenack
Occasional Contributor
Joined 16 years ago
User Profile
User Widgets
Contributions
Re: AQTime combined with dynamic package loading results in serious crash
After some correspondation by email, at first it seemed the problem was caused by the aqtime IDE plugin extension being compiled with XE2 Update2. I got a new bpl (to test) and the problem appeared to have gone away. BUT as it turned out, I had also disabled my exception hooking code meanwhile. And this again turned out to be the real issue. What actually hgappened is that the initialization code installed for exception hook, also was executed when my bpl was loaded by the IDE (support for some designtime package). And this probably caused a mixup with the IDE's own exception handling routines, and crashed the IDE in a very crude way. Also de XE2 internal debugger seemed to have trouble with my exception handling code. The solution was to extend the initialization routine so my hooks won't be installed: 1) if the bpl was loaded by BDS.EXE 2) if DebugHook<>0 I must say Smartbear (support at automatedqa.com) took my report very seriously and helped to fix the issue. Great support. Thanks David.3KViews0likes0CommentsRe: AQTime combined with dynamic package loading results in serious crash
Ah... Yes I got a message stating he will look into the case, so except from your reply in the forum no other hints/suggestions have arrived yet. The mails have to go through our info@ mailbox which makes them appear the next day when our secretary forwards them. I asked to send replies to my work and private email accounts too, but I just got the message today ;) I'll send my status updates by email from now.3KViews0likes0CommentsRe: AQTime combined with dynamic package loading results in serious crash
Status update It appears in one of my bpls for multithreading I had 2 CreateSemaphore calls, and the application forgot to close the handles. The 2nd time the application was started (or maybe even in the IDE) this seems to create some kind of conflict causing the external exception. I found the resource leaks using AQTime -NoOpenApp parameter, not running ot from the IDE but separately. Next I added the required code to close the semaphores, and it seems like the IDE crash problem is gone. I will let you know if -after some more serious retesting- the problem is really gone. Maybe you can confirm the External Exceptions may happen because of things like this.3KViews0likes0CommentsAQTime combined with dynamic package loading results in serious crash
Hi We are currently using AQTime pro 7.30.537.64 (64 bit edition, floating license) and are experiencing problems that cause the entire IDE to freeze or crash. Our app uses dynamic package loading as a plugin system, and during the loading of one of the packages (that requires NexusDB3.103) the entire IDE crashes with an EExternalException in module aqReporter.dll ast 00017E63. External exception C0000026. BTW The app is NOT started using any profiler, just the normal IDE debugger is started. AQTIme integration is present in the IDE. so.. 1) COmpile the app, start debugging 2) breakpoint on loadmodules -> no problem I can debug my app, nu dynamic packages are loaded 3) modules get loaded some get loaded OK 4) tries loading my DB plugin package -> Bang. IDE crash in aqreporter.dll as mentioned before, 5) App dies. And I can do this repeat this each time. OS? : Both WinXP64 and WinVista64 same problem IDE?: RADStudioXE2 Update3 When I rename the AQTIme app folder to aqtime7.b00 and restart the IDE the AQTime integration as well as the problem is gone, and I can succesfully debug the dynamically loaded packages. When I run the app without debugging, also there appears to be no problem. I've read in another thread on these forums here there might come/be an 3.4 version of AQTime7, maybe this problem was addressed there too? Also I seems I'm not the only one experiencing this problem: https://forums.embarcadero.com/thread.jspa?threadID=66702 I have attached process explorers' list of DLL's at the thime thr BDS displays the external exception. and a screenshot of the active threads after the crash displayed. I hope it will help to pin down this nasty problem. Regards Hans Hasenack15KViews0likes9CommentsRe: How to track down memory leak when AQtime gives class as "VCL native memory"
Dear Margaret We use AQTime pro 7.0. and since I am experiencing some trouble I was looking for an update. My app and the webpage says the latest release is 7.30.537.64 So I guess the 7.40.xx.xx is till being tested at the moment. I'll post my problem in a separate thread.1.8KViews0likes0CommentsRe: Windows Waiting calls, remove time spent in there
Somehow I expected this answer already... I got the same reply from Allen bij email. :) Anyway - let's hope for a quick implementation of my Phenom X4 processor, and for a fix in order to avoid having to run Win7x64 (or WinXPx64 for that matter) in debugging mode. :( When an app crashes, the whole system freezes because it jumps into debugging mode on a serial port...): Regards - Hans2.7KViews0likes0CommentsRe: Windows Waiting calls, remove time spent in there
I have experimented a bit with EnableProfiling(Enabled:boolean) and with this it's also not possible to "skip" the elapsed time. It simply does not record subroutine calls, but still measures the elapsed time. What about a routine like PauseProfileTimer(Paused:boolean). Would that be hard to implement? (Still I do not know how elapsed time actually is measured). With this routine I could write a wrapper around WaitForSingleObject like this: function MyWaitForSingleObject(hHandle: THandle; dwMilliseconds: DWORD): DWORD; begin PauseProfileTimer(True); try Result:=windows.WaitForSingleObject(hHandle,dwMilliseconds); finally PauseProfileTimer(False); end; end; Regards - Hans6.4KViews0likes0Comments