AnsweredAssumed Answered

Crashes related to leaks reported in console - coding error?

Question asked by decourseym on Apr 15, 2009
Latest reply on Apr 16, 2009 by TSGal

Summary

Crashes related to leaks reported in console - coding error?

Description of the issue

FMP Product:  Filemaker Pro Advanced 9.0v3    OS System: OS X v10.5.6 I am experiencing persistent crashes of old files, new test files (with and without data), and on FMP open.    Steps taken: after UQ on new file creating, created test file which also crashed, tested two other files, one new, one several years old. These crashed quickly, (one died while sitting in background as I created run notes.) so quit FMP which then crashed on reopen.  Then restored earlier copies to another system running Panther and Filemaker Pro Advanced 8.5.  Files working fine there.  Talked to Apple support, removed Safari beta and changed DNS Server.  Speed improved but did not address FMP issues.   Took system to Apple and verified this is not a hardware issue, (new logic board and clean install last February when had UQ's with FMP along with hardware issues.)  Verified that hard drive and ram are fine. Verified that not an OS issue.  Console reports just leaking errors whenever Filemaker is open.     Apple Genius Bar comments:  "Looking at the Console log for Filemaker it appears a piece of code is not finishing itself [no backslash to close command] causing a "Leak." At this point we've verified the OS and hardware are in tip-top shape and have gone so far as to replace the logic board. RAM passed all tests, as did the hard drive. Based on information from a Cocoa Developers group it appears there is a loose piece of coding which is causing the problem." Don't know were to go from here.   Am able to open FMP  and files without UQs, but  console errors continue, and I do not trust FMP on Leopard. Ideas welcome.  Thank you.

Outcomes