BugReport: ShareMem vs System.ShareMem
Posted: Tue Aug 14, 2018 9:29 am
Hey, just want to inform you, that there seems to be a bug in the current madExcept-versions when using newer Delphi-Versions and custom-dlls.
When closing the application there is an exception in BORLNDMM.DLL.
This happens because the unit "ShareMem" has to be the first unit in the uses-part of the application. But when activating madexcept, it is registered "on top" of this unit what causes the problem.
I think this is a new issue, because with older delphi-versions this works fine, difference: ShareMem (old) vs System.Sharemem (new).
Just in case other developers using the new delphi versions get similar problems, just make sure, that System.ShareMem is on top or replace it with the old alias ShareMem only.
When closing the application there is an exception in BORLNDMM.DLL.
This happens because the unit "ShareMem" has to be the first unit in the uses-part of the application. But when activating madexcept, it is registered "on top" of this unit what causes the problem.
I think this is a new issue, because with older delphi-versions this works fine, difference: ShareMem (old) vs System.Sharemem (new).
Just in case other developers using the new delphi versions get similar problems, just make sure, that System.ShareMem is on top or replace it with the old alias ShareMem only.