Icon View Incident Report

Serious Serious
Reported By: Jeremy Martin
Reported On: 4/8/2005
For: Version 4.19 Build 1
# 2023 Running SQL INSERT Statements Against a TADOTable with the ODBC Driver Causes a Memory Leak

Memory Usage. I don't know if there is a leak but both the MemUsage and the Virtual Memory Size Just keep growing for DBSrvr.exe until the sessions start to AV in the server from lack of memory. The only way to fix it is too Restart the DBISAM Service. Just to give you an idea if I insert 11000 records into a table it requests 2GB of Virtual Memory and dies.

Comments Comments
The ODBC driver was allocating a statement handle but not freeing it up properly.

Resolution Resolution
Fixed Problem on 5/4/2005 in version 4.20 build 1

Products Affected Products Affected
DBISAM ODBC Client-Server
DBISAM ODBC Client-Server with Source
DBISAM ODBC Standard with Source