After Migration > random EAccessViolation errors
Posted: Mon 17 Sep 2018 12:26
Before changing all IBX components to IBDAC >> this project was running rock stable for 10+ years.
(Delphi 7 + FB 2.5 ; 50+ forms ; 200+ data componenst)
Now it is crashing at random places, when the program tries to access some local Firebird (2.5.8) data.
Even simple code like: DBDB.ping; or Customers.Open; can cause it, but not always.
(Running debugging step by step)
Project yyyyy.exe raised exception class EAccessViolation with message 'Access violation at address 400027A2 in module 'rtl70.bpl'. Write of address 00435DCA'. Process stopped. Use Step or Run to continue.
Timer...
try
dt2.DBDB.Ping;
>> Result := dt2.DBDB.Connected ; // stops here for example
if moving the mouse over "Connected" >> it shows True !!
- yes, the database itself is at local place C:\...
- yes, it has connected first, loaded all kind of data and all this happens AFTER that (in a timer)
- yes, I use try ... except ... to catch the error
I really have no more ideas how to debug it further.
Can it be that the component is incompatible with FasttMM4.pas memory manager?
(Delphi 7 + FB 2.5 ; 50+ forms ; 200+ data componenst)
Now it is crashing at random places, when the program tries to access some local Firebird (2.5.8) data.
Even simple code like: DBDB.ping; or Customers.Open; can cause it, but not always.
(Running debugging step by step)
Project yyyyy.exe raised exception class EAccessViolation with message 'Access violation at address 400027A2 in module 'rtl70.bpl'. Write of address 00435DCA'. Process stopped. Use Step or Run to continue.
Timer...
try
dt2.DBDB.Ping;
>> Result := dt2.DBDB.Connected ; // stops here for example
if moving the mouse over "Connected" >> it shows True !!
- yes, the database itself is at local place C:\...
- yes, it has connected first, loaded all kind of data and all this happens AFTER that (in a timer)
- yes, I use try ... except ... to catch the error
I really have no more ideas how to debug it further.
Can it be that the component is incompatible with FasttMM4.pas memory manager?