Delphi Rio Release 1 issues

delphi package - automated exception handling

Delphi Rio Release 1 issues

Postby simpsons » Sun Feb 17, 2019 7:29 pm

Hi,

I can not use the current madExcept 5.0.0 (2.8.8.4) beta with Delphi Rio Release 1 (edit: same behaviour with 5.0.0 (2.8.8.0) from 2018-11-29).
Everything compiles fine as a 32bit application, but the executable does not show any memory leaks or exception dialogues anymore.
Furthermore the executable (or threads or anything) is still running in the background after close and cannot be deleted or recompiled.
The app process is not shown in the Windows task manager.

I cannot reinstall madExcept either, because the last start of my app seems to have madExcept32.dll still locked.
ProcExplorer shows that the dll is still loaded by the app.
Hmmmmh, why is the dll loaded anyway as all checkboxes are checked to link-in madexcept.

I've checked and observed the exact same behaviour on two Windows 10 64bit PCs.

Anything that I can do to provide more infos?
simpsons
 
Posts: 12
Joined: Tue Sep 30, 2014 8:15 pm

Re: Delphi Rio Release 1 issues

Postby simpsons » Sun Feb 17, 2019 8:24 pm

OK, this is triggered by the setting "instantly crash on" + "buffer overrun".
Switching this off and the app reports ressource leaks again.

But the question still stands, why the dll is loaded, when madExcept should be linked into the app...
simpsons
 
Posts: 12
Joined: Tue Sep 30, 2014 8:15 pm

Re: Delphi Rio Release 1 issues

Postby madshi » Mon Feb 18, 2019 11:13 am

Is this a new problem with Release 1? Can you reproduce this with a brand new (almost empty) test project?
madshi
Site Admin
 
Posts: 10010
Joined: Sun Mar 21, 2004 5:25 pm

Re: Delphi Rio Release 1 issues

Postby simpsons » Mon Feb 18, 2019 12:50 pm

Jepp, simple project with just two buttons, one triggering a memory leak, the other one an exception.
If BufferOverrun is on, the executable is invisible in the task manager after close, but the process is still there (procexp64 sees it) and has madexcept32.dll loaded and locked.
No memory leaks are reported.
I get more than the one expected exception dialogs.

Switching BufferOverrun off, everything is working fine.
Memory leak is reported after close and I get only one exception dialog.

But with either setting, the madexcept32.dll is loaded and is still blocking the process after the exception.
When I click on "continue" in th exception dialog, the form doesn't show up anymore and the process is still running in the background.
See screenshot of procexp64.
Attachments
2019-02-18_135441.png
2019-02-18_135441.png (9.63 KiB) Viewed 404 times
madExceptBufferOverrun.zip
(53.29 KiB) Downloaded 21 times
simpsons
 
Posts: 12
Joined: Tue Sep 30, 2014 8:15 pm

Re: Delphi Rio Release 1 issues

Postby madshi » Mon Feb 18, 2019 1:31 pm

Ok, thanks. This could be a bug in madExcept, or a bug in Rio Release 1, can't say right now. I'll have a look at that when I find some time, might take a couple of days, though. For the time being, it might make sense to disable the "instantly crash" feature.
madshi
Site Admin
 
Posts: 10010
Joined: Sun Mar 21, 2004 5:25 pm


Return to madExcept

Who is online

Users browsing this forum: No registered users and 6 guests