Figuring out why FileMaker is crashing can require some sleuthing to rule out possible issues.
Basic diagnostic tests to perform when you get frequent crashes or “Hangs”:
Does the crash only occur with a specific file?
Test by creating a small sample file and see if opening it and working with it also generates a crash. If it crashes too, the problem likely lies with the computer or it's installation of FileMaker. If it does not crash, it becomes more likely that there is a problem with the file.
What is reported when you recover the file?
The file could be damaged. Not only can file damage cause crashes, but the crashes (or forced quits after a "hang") can damage your file. You may need to test a recovered copy to see if it works without crashing.
Things to keep in mind about Recover:
- Recover does not detect all problems
- Recover doesn't always fix all problems correctly
- Best Practice is to never put a recovered copy back into regular use or development. Instead, replace the damaged file with an undamaged back up copy if this is at all possible. You may have to save a clone of the back up copy and import all data from your recovered copy to get a working copy with the most up to date information possible.
Does it always crash when you are doing the same thing with your file?
That may point to a specific layout, script, operation that interacts with your Operating system or other applications...
If you start with the SHIFT key down at startup, only Apple extensions will load and diagnostics are done on the hard drive.
If you create a new user in Apple Menu > System Preferences > Accounts, logout of your regular user and log in to test user. And Test.
You can determine if it is a system wide problem or a user problem.
There are maintenance utilities that can solve problems - AppleJack and Onyx are two such utilities.
Caches, especially font caches, can become corrupt. Deleting them can solve crashing problems.
Font Nuke is a free utility to do this http://www.jamapi.com/pr/fn/
The Computer Guy, Seattle