9 Replies Latest reply on Feb 21, 2012 9:36 AM by Vincent_L

    Filemaker Crashes Constantly

    lannycook

      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.

        • 1. Re: Filemaker Crashes Constantly
          philmodjunk

          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:

          1. Recover does not detect all problems
          2. Recover doesn't always fix all problems correctly
          3. 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...

          • 2. Re: Filemaker Crashes Constantly
            lannycook

            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?

            The crashes appear to be completely unpredictable and repeatable.  It can crash at almost any point, doing just about anything.  I can recover a file.  Make the same changes to the last good file and it won't crash. 

            I am now starting again from scratch.  I am copying from the last recovered file everything that I can.  Is copying everything, or anything in particular, from a recovered file a bad idea?

            • 3. Re: Filemaker Crashes Constantly
              Vincent_L

              Hi,

              Make a data-less clone, and use it a bit. Does it crashes ?

              I had crashes due to a paricular invisible character in a filed once, it drove me nuts for 3 hours. That charcaters was of the kind of Ç in unicode by coded stangely. In unicode you can have character like Ô that are in fact coded as ^O Filemaker hates them. When I got rid of those (that came from termial file pathnames) it was stable again !

              • 4. Re: Filemaker Crashes Constantly
                philmodjunk

                I find filemaker to be very stable. Crashes occur very seldom for me. However, the causes of a crash when they do occur can be tricky to track down. The list of suggestions I posted earlier is intended to help you narrow down the cause.

                • 5. Re: Filemaker Crashes Constantly
                  lannycook

                  I started a DB with no data and tried adding just enough data to be able to run some of the application.  That also caused crashes.

                  I separated the data from the layout, value lists, code, etc.  Same problem. 

                  If anything it is getting worse.  I have actually lost a great deal of code and time in the last week.

                  Nothing else crashes on the computer.  Nothing else hangs up.  The computer is otherwise completely stable.

                  This leads me to believe that the installation of Filemaker is suspect.  No errors occurred during the installation.  Nothing out of the ordinary happened although it was my first ever install of Filemaker. 

                  Does the install seem suspect?  Can I just reinstall from the original file or should I download again?  How does this affect my license?

                  To refresh, my computer is running Mac OS 10.6.8, Filemaker 11v4 Pro Advanced.

                  Thanks,

                  Lanny

                  • 6. Re: Filemaker Crashes Constantly
                    philmodjunk

                    It's not clear from your post whether or not you tried this test:

                    Launch FileMaker without opening any existing files.

                    Use New database to create a brand  new, small test file. You aren't trying recreate your existing file, You are creating just enough of a database file to see if it will be stable or crash. Do not import, or copy/paste anything from any other file or application with this file.

                    See if it is stable or crashses frequently.

                    • 7. Re: Filemaker Crashes Constantly
                      user15307

                      Lanny Cook

                      Thank you for your post.  

                      I realize the cause of an issue like this is extremely difficult to pin down, and want to assure you that FileMaker Pro 11v4 Advanced can run without crashes or errors on Mac OS X, 10.6.8.

                      It is very possible that a file in your FileMaker installation is corrupt.  One way to narrow this down is to try launching FileMaker from a newly-created user on that machine.  If it does work on that user with a fresh file, then try one of your other files.

                      Even though the computer is "otherwise completely stable", there may be a conflict in resources.  If FileMaker Pro 11 Advanced still quits unexpectedly in a new user, you should try an uninstall and re-install. To uninstall, close FileMaker and then drag to the trash the FileMaker Pro 11 Advanced folder in the Applications folder.   

                      You may also check in the Library of your user account for FileMaker files to delete prior to the re-install. Look in youruser/Library/Preferences folder for any "com.FileMaker.xxx files". 

                      Doing a re-installation from the installer previously downloaded or by downloading the FileMaker ESD again can be done without affecting EULA compliance, you will be prompted to enter the License Key again, and, if your FileMaker Pro is an upgrade, also will be prompted for the License Key of the qualifying FileMaker product.

                      TSTuatara

                      FileMaker, Inc. 

                       

                       

                      • 8. Re: Filemaker Crashes Constantly
                        lannycook

                        Thanks for the responses.

                        I have tried to build a database from scratch.  I have put very little data into it and played around.  No crashes.

                        Obviously I have to have a DB that does something.  And the something is very clear. 

                        So I have tried to copy objects from my existing work, instead of re-doing all of it, and then playing with it.  I did this meticulously by adding one object at a time and then testing it.  The inter-related nature of the objects and scripts didn't allow completely testing everything, so I wasn't sure when or if I was adding something bad back.

                        I did finally narrow it down to one object, a layout.  There was something corrupt about it.  I have re-built that object from scratch, for the most part, and have not had any crashes since.

                        It is a bit disconcerting that Filemaker doesn't tell you (or even know) which object is corrupt.  Also what caused the corruption in the first place.  I understand that some things are outside the ability of Filemaker to control, like system crashes caused by other programs, power-outages, etc.

                        It would seem though that Filemaker during its recovery program should be able to tell us which object(s) were found to be corrupted.  I saw error messages in the log file but the objects were not mentioned.  It would be helpful to know which objects were corrupt and which might be re-usable.  Somewhere in the documentation is says to not used the recovered file but to use the last known good backup.  And then copy from the recovery file to get your work back.  I was doing that but apparently I was copying the corrupt object back in.

                        In the end, the problem is solved, I believe but I am very reluctant to use anything from a recovered file.  Which means I backup my work about every 10 minutes or after any significant amount of work.  I even stop in the middle of productive sessions to backup.  Not ideal but workable.

                        Thanks again,

                        Lanny

                        • 9. Re: Filemaker Crashes Constantly
                          Vincent_L

                          Glad you nailed it,

                          But do you still have the corrupt file ? Keep it like a relic because it could be very usefull for the FMP community :

                          I think that rather than redoying from scracth the layout, you may have been able to copy and paste it with ClipManager.

                          Assuming there was no image in it, copying it to clip manager would force FMP to create a clen html. Then editing it in ClipManger, by just adding a line, and then copy it back to a new layout would perhaps save the work.

                          If you don't mind, please try the free demo http://www.myfmbutler.com/index.lasso?p=422

                          If you can proved that the resulting fixed db works, then it migh validate the XML cleaning process and save a lot of time for other people.

                          Thanks