View Incident Report

Minor

Reported By: Roy Lambert
Reported On: 11/7/2008
For: Version 2.02 Build 2

# 2844 Rows Locked Manually Using LockCurrentRecord Method Can Cause Memory Leak

I'm implementing UserCount (as kindly supplied by Terry) and I get a memory leak.....

Stack trace of when this block was allocated (return addresses):
402DFE [System][@GetMem]
40442B [System][TObject.NewInstance]
4047F2 [System][@ClassCreate]
404460 [System][TObject.Create]
4CF843 [edbrow][TEDBRowLocks.IncCount]
4CF8C9 [edbrow][TEDBRowLocks.Insert]
58E40E [edblocal][TEDBLocalCursor.LockRow]
5AB26A [edbcomps][TEDBDataSet.LockCurrentRecord]
5B1BFD [E:\ElevateDB Support\UserLocks\UserCount.pas][UserCount][TUserCount.LockSlot][244

Comments and Workarounds

The workaround is to call the UnlockAllRecords method before closing the dataset.

Resolution

Fixed Problem on 11/7/2008 in version 2.02 build 3

Products Affected

ElevateDB LCL Standard with Source
ElevateDB VCL Client-Server
ElevateDB VCL Client-Server with Source
ElevateDB VCL Standard
ElevateDB VCL Standard with Source
ElevateDB VCL Trial

More Support Options

Search Incident Reports

Support Forums

Frequently Asked Questions

Technical Bulletins

Technical Articles

Product Manuals

Roadmap