Please compare what you are experiencing to this previously logged report and let us know if it looks like the same issue or not: FileMaker Server
This is one of many acknowledged bugs that can be found in the Known Bug List here in the Report an Issue section of the forum.
It can also be downloaded as a database file from: http://www.4shared.com/file/8orL8apk/FMP_Bugs.html
Also, FileMaker released an ODBC/JDBC updater that is supposed to cure "some memory leaks" (though not the above issue.) Have you downloaded and installed it? (Not part of the v3 updater, it's a separate download.)
@PhilModJunk. THis is not the same problem i think, but the behavior is about the same.
This bug is not in the FMP_Bugs datafile.
It is the same as http://forums.filemaker.com/posts/14eb655faa.
The problem is platform independent. We have found it with our clients at different platforms from Mac to Windows XP and Up. Also in Advanced, Pro and runtime.
We also use Fusion Calendar and we and our clients are severely handicapped by this Bug.
The Fusion Calendar looks for update at a short interval. In our case the memory use is increasing in a rate of 1 Mb a minute and the user is not doing anything. If the user scrolls thru the weeks in the calendar the increase can be as much as 20 Mb per action.
This can go on until Filemaker runs out of available memory and then it crashes. Sometimes corrupting the database and the client looses information.
The guys at Fusion (Reactron NZ) are working on a workaround, but they are severely handicapped by the earthquake early this week and it is after all a Filemaker bug.
I have done some test with FM10.
The same behavior and the same speed of increased memory use. The test was on the Mac platform, OS 10.6.6
So this bug is as old as FM 10.
A memory leak issue does exist when using ODBC with FileMaker Pro/Server as we recently replicated the problem on a consistent basis (thanks to customer files and logs). Our Development department is investigating this, but no additional information is available at this time.
I know no additional information is available at this time. However as this is a grave and crippling issue, could an exception be made and a guess perhaps be hazarded by the developers perhaps as to when his bug may perhaps be fixed?
Thank you for your post.
Since FileMaker, Inc. is a wholly-owned subsidiary of Apple Computer, we are not to discuss future releases. I can only verify that the problem is now reproducible and has been sent to Development.
Hello TS Gal,
That is disappointing. It doesn't matter to me who you are a subsidiary of. All we want is a progress update on fixing this bug since we have an acute and untenable situation here vis a vis our customers. They and we need to know if we're looking at days, weeks or months before this is fixed. Your product is at the heart of our business, and our business is under a lot of pressure at the moment because of an issue with your product. If this issue cannot be solved in a time frame that we can survive, then we have to set things in motion to move our database to another platform ASAP. At this point, it's not just a nuisance, it's about making sure our business survives. I hope you can appreciate this.
I agree that this es very annoying. With a bug in this category:
- kills production
- is reproducible
- mega annoying
The Developer *should* be asked for a timeframe, whether he likes it or not. Im a developer too, and "its finished when its finished"! YES. But here a guessimate would be nice and if I was the developer I would certainly have understanding for that!
Question for Mr. Van Den: If I simply connect from Filemaker to a simple SQL Datasource via the "External Data Sources" menu and then I just import a table; am I likely to then suffer this leak?
Since the squeaky wheel gets the kick (or replaced), just adding another voice that this is a serious issue that needs addressed, and is not "Risk Level: Low".
After the recent ODBC update, which mention that the SQL leak was solved, we hoped it would also be solved for our problem. Not so. It is still there. We do not use ODBC but the API for the plugin.
This is for us and other users of plugins who uses SQL a major problem.
If I look at this forum this problem is more than a year old.
Please solve this.