AnsweredAssumed Answered

Is there a workaround to FileMaker ODBC Driver memory leak?

Question asked by grzesgbc on Dec 6, 2017
Latest reply on May 15, 2018 by TSGal

Product and version

FileMaker Server 16.0.3

FileMaker ODBC Driver version 16.0.19

OS and version

Windows Server 2008 R2 Standard Service Pack 1

Hardware

HP ProLiant DL380 G7

Description

Using ODBC to import data from a hosted FileMaker database to an Excel spreadsheet causes a memory leak. Each time the data table imported to excel is refreshed 40 handles are used and not released.

How to replicate

1. Create a new data source DSN using FileMaker ODBC driver on a client computer. The new data source should point to a hosted FileMaker databsse.

2. Create a new Excel spreadsheet and use DSN to connect to the hosted FileMaker database and import data.

3. Refresh the data table in Excel and check how the number of handles used increased. The number of handles used by Excel can be seen in Windows Task Manager.

Each time the data table imported to excel is refreshed the same number of handles should be used and released. The number of used handles should not increase.

Each time the data table imported to excel is refreshed another 40 handles are used and not released. After 10 times the number of used and not released handles increases by 400.

Notes

I have already reported this issue in 2012:

FileMaker ODBC driver memory leak 

Outcomes