AnsweredAssumed Answered

Filemaker Crashes Constantly

Question asked by lannycook on Feb 15, 2012
Latest reply on Feb 21, 2012 by Vincent_L

Summary

Filemaker Crashes Constantly

Product

FileMaker Pro

Version

Filemaker 11v04 Pro Advanced

Operating system version

Mac OS X 10.6.8

Description of the issue

Filemaker crashes constantly during just about anything.  It has crashed during writing scripts, designing the database, modifying layouts, navigating through layouts, etc.

I never know when it is going to crash. 

I can recover the database with no errors sometimes.  Sometimes not.  I always go back to what I think is the last uncorrupt and unrecovered database.  I then try to copy what I lost (if anything) to the old database and then continue.

Obviously I save often.  Still I am having to re-do far too much work.  This last crash was too costly, meaning I lost a great deal of work.  I cannot continue until something is resolved.

This product was purchased within the last 2 weeks.

Posted after PhilModJunk answer - The web site won't let me respond to him.  The post box is missing.

Your answer doesn't sound too encouraging.  It sounds like there are many, many things that could cause crashes.  Am I correct in assuming that this is not a very stable program?

The last crash occurred when I was saving changes to a script that was attached to a button on a layout in Form View.  This has happened before and I was able to add the changes again without an error.

Recover sometimes reports an error, sometimes not. Here is a sample.

2012-02-15 11:49:32.441 -0800     E2_Admin.fp7     8452     ERROR: Page 299 invalid structure, dropping it
2012-02-15 11:49:32.450 -0800     E2_Admin.fp7     0       Dropped page starts with data of type: layout
2012-02-15 11:49:32.468 -0800     E2_Admin.fp7     0     Scan complete, found 335 page(s) to process
2012-02-15 11:49:32.473 -0800     E2_Admin.fp7     8455     ERROR: Page 329 contains duplicate data, dropping it
2012-02-15 11:49:32.477 -0800     E2_Admin.fp7     0       Dropped page starts with data of type: layout
2012-02-15 11:49:32.481 -0800     E2_Admin.fp7     8455     ERROR: Page 25 contains duplicate data, dropping it
2012-02-15 11:49:32.485 -0800     E2_Admin.fp7     0       Dropped page starts with data of type: layout
2012-02-15 11:49:32.489 -0800     E2_Admin.fp7     8455     ERROR: Page 334 contains duplicate data, dropping it
2012-02-15 11:49:32.493 -0800     E2_Admin.fp7     0       Dropped page starts with data of type: layout
2012-02-15 11:49:32.497 -0800     E2_Admin.fp7     8455     ERROR: Page 335 contains duplicate data, dropping it
2012-02-15 11:49:32.501 -0800     E2_Admin.fp7     0       Dropped page starts with data of type: layout
2012-02-15 11:49:32.505 -0800     E2_Admin.fp7     8455     ERROR: Page 336 contains duplicate data, dropping it
2012-02-15 11:49:32.508 -0800     E2_Admin.fp7     0       Dropped page starts with data of type: layout
2012-02-15 11:49:32.512 -0800     E2_Admin.fp7     8455     ERROR: Page 337 contains duplicate data, dropping it
2012-02-15 11:49:32.516 -0800     E2_Admin.fp7     0       Dropped page starts with data of type: layout
2012-02-15 11:49:32.520 -0800     E2_Admin.fp7     8455     ERROR: Page 338 contains duplicate data, dropping it
2012-02-15 11:49:32.524 -0800     E2_Admin.fp7     0       Dropped page starts with data of type: layout
2012-02-15 11:49:32.528 -0800     E2_Admin.fp7     8455     ERROR: Page 339 contains duplicate data, dropping it
2012-02-15 11:49:32.535 -0800     E2_Admin.fp7     0       Dropped page starts with data of type: layout

Do these errors point to anything in particular?

I don't use databases that were recovered or ever crashed.  I go back to the latest "good" copy that I have and either remake the changes or copy from the recovered database.

I read an earlier post that suggested "spaces" in indexed fields could cause crashes.  Is that a possibility?

Steps to reproduce the problem

Not sure.  Too prevalent.

Expected result

No crashing.

Actual result

Crashes.

Exact text of any error message(s) that appear

By crashing I mean the program just closes with NO ERROR MESSAGES. I often get the message that the program quit unexpectedly and what would I like to do.  I have sent info to FM at least a couple of times but not sure where it goes.

Workaround

Nothing.  I have no idea why it crashes.

Outcomes