Page 1 of 1

Bug in latest version: unable to close due to unfinalized statements or unfinished backups

Posted: Sat 23 Mar 2019 15:45
by Max Terentiev
Hi,

After installing latest VirtualDAC version 10.5.13 I have (time to time) this exceptions while opening Virtual Query:

unable to close due to unfinalized statements or unfinished backups

OR

Access Violation

Debugger show exception somewhere in VirtualDac units.

After rolling back to older version 10.3.8 problems gone.

Here is my code for the query:

Code: Select all

ProxyDS=new TVirtualDataSet(NULL);
ProxyDS->FieldDefs->Add("No",ftInteger,0,false);
ProxyDS->FieldDefs->Add("IP",ftString,64,false);
ProxyDS->FieldDefs->Add("Threads",ftInteger,0,false);
ProxyDS->FieldDefs->Add("ConnAttempts",ftInteger,0,false);
ProxyDS->FieldDefs->Add("ConnFailsInRow",ftInteger,0,false);
ProxyDS->FieldDefs->Add("ConnFailsTotal",ftInteger,0,false);
ProxyDS->FieldDefs->Add("MsgSent",ftInteger,0,false);
ProxyDS->FieldDefs->Add("Effeciency",ftInteger,0,false);
ProxyDS->FieldDefs->Add("Status",ftString,100,false);
ProxyDS->FieldDefs->Add("ID",ftInteger,0,false);
ProxyDS->FieldDefs->Add("Host",ftString,64,false);
ProxyDS->FieldDefs->Add("Deleted",ftBoolean,0,false);
ProxyDS->AutoCalcFields=false;
ProxyDS->ReadOnly=true;
ProxyDS->OnGetRecordCount=ProxyDSGetRecordCount;
ProxyDS->OnGetFieldValue=ProxyDSGetFieldValue;
ProxyDS->Open();

ProxyQry=new TVirtualQuery(NULL);
ProxyQry->AutoCalcFields=false;
ProxyQry->ParamCheck=false;
ProxyQry->ReadOnly=true;
ProxyQry->FetchAll=false;
ProxyQry->SourceDataSets->Add(ProxyDS,"RunTimeProxyList");
ProxyQry->SQL->Add("SELECT * FROM RunTimeProxyList WHERE Deleted=false");
ProxyQry->Open(); // <---- exception here !!!!
To reproduce problem run above code in loop:

- create and setup as shown above
- open query
- close & free ProxyQry and ProxyDNS
- run again.

You should get similar exception soon.

Re: Bug in latest version: unable to close due to unfinalized statements or unfinished backups

Posted: Mon 25 Mar 2019 12:38
by MaximG
We checked the work of VirtualDAC according to your description. Unfortunately, we could not reproduce the described issue. For further issue investigation, please send the full source code of your test project, execution of which causes the issue. For your convenience, please use the e-support form : https://www.devart.com/company/contactform.html

Re: Bug in latest version: unable to close due to unfinalized statements or unfinished backups

Posted: Wed 27 Mar 2019 12:34
by DanielNTM
Dear All,

Since several days, we encounter the exact same problem than has been described by Max Terentiev.

If we use VirtualQuery in a loop, it makes the software to crash.

We could reproduce this problem in a test software. I'll sent it through the e-support right now.

Thank you for your help.

Regards

Re: Bug in latest version: unable to close due to unfinalized statements or unfinished backups

Posted: Fri 29 Mar 2019 15:38
by MaximG
Thank you for the provided example. Unfortunately, we couldn’t reproduce the issue you described by following it. We will try our best to find a way to get additional debug data which can help us to single out the cause of the issue. We will let you know the results as soon as possible.

Re: Bug in latest version: unable to close due to unfinalized statements or unfinished backups

Posted: Mon 13 May 2019 21:34
by faktoral
Could there be an error caused by sqlite?

Re: Bug in latest version: unable to close due to unfinalized statements or unfinished backups

Posted: Wed 15 May 2019 19:38
by faktoral
MaximG wrote: Fri 29 Mar 2019 15:38 Thank you for the provided example. Unfortunately, we couldn’t reproduce the issue you described by following it. We will try our best to find a way to get additional debug data which can help us to single out the cause of the issue. We will let you know the results as soon as possible.
Could there be an error caused by sqlite?

Re: Bug in latest version: unable to close due to unfinalized statements or unfinished backups

Posted: Thu 16 May 2019 14:46
by MaximG
VirtualQuery is built using the SQLite engine. The above error might occur in that engine. Please compose and send us a small sample project so that we could reproduce the issue. For your convenience, please use the e-support form https://www.devart.com/company/contactform.html