Icon View Incident Report

Serious Serious
Reported By: Danny Humphress
Reported On: 12/23/2016
For: Version 4.43 Build 3
# 4478 Session Name Assignments Can Exprience Access Violations in Multi-Threaded Applications

I am moving from Delphi 10 Seattle to Berlin and am getting an error in one of my apps, which creates and frees numerous DBISAM sessions and databases. The app runs fine when compiled with Seattle but I get an AV error in Berlin. Im using DBISAM 4.43 Build 3.

Here is the call stack:

:77397193 ntdll.RtlEnterCriticalSection + 0x13
:00759026 OSEnterCriticalSection + $6
:0083a1c9 TDBISAMDatabase.CheckSessionName + $6D
:0083a9e8 TDBISAMDatabase.SetSessionName + $48
System.TObject.Free


Comments Comments
This bug had to do with database components being destroyed that are owned by a session component. Therefore, if you were instantiating any TDBISAMDatabase components like this:

MyDatabase:=TDBISAMDatabase.Create(MySession);

then you would run into this issue.


Resolution Resolution
Fixed Problem on 12/24/2016 in version 4.43 build 4


Products Affected Products Affected
DBISAM VCL Client-Server
DBISAM VCL Client-Server with Source
DBISAM VCL Standard
DBISAM VCL Standard with Source
DBISAM VCL Trial

Image