5 Replies Latest reply on Aug 21, 2013 4:57 PM by gdurniak

    Is it FMP or Apple that's the problem?

    Maclurv

      I am in the process of rebuilding a file (fmp12). I am able to copy the layout from the old version (also fmp12) to create the layout in the new version. Or, at least I was. Now, everytime I copy the layout to the clipboard, the program crashes and I get one of those lovely reports about which I understand very little.

       

      Does this abrupt crashing mean that my copy of FMP may need to be uninstalled and a clean copy put back on? Given that I am rebuilding a file because of corruption problems in the old one, does the abrupt quitting corrupt my new file? So far I haven't gotten that message upon re-opening about it not being shut down correctly. Since I was able to copy other layouts, might it just be this particular layout that is a problem? Or is my computer system going nuts (Mountain Lion, 10.8.4)?

       

      This isn't a small file to rebuild and I don't want to be wasting any effort and time if I can prevent something from happening.

       

      Thanks for any insight.

        • 1. Re: Is it FMP or Apple that's the problem?
          Stephen Huston

          The problem may well be that the layout objects you are trying to copy contain some corruption, which is causing the crash.

           

          The message that the file was not closed properly is standard following a crash/improper closing of the application; when FMP closes a file properly, it resets a flag in the file as it closes it, and if that file-level flag is not "closed" when the file is next opened you get that warning. Usually it means nothing more than that the program crashed, but it is there to remind you that the file as gone through a bad experience and something might have happened to it.

           

          Do a lot of backing up as you  rebuild critical stuff. Once I know there is likely to be crash risks, I tend to do a manual backup script just before every high-risk operation, and routinely roll back to a copy of the previous backup any time there's a crash.

          • 2. Re: Is it FMP or Apple that's the problem?
            Maclurv

            Thanks. I am trying to do that. Now, it happened as I used the command-Copy on some elements. I did not do the 'select all' but have been doing individual bits. Doing okay until this element. Perhaps they are the corrupted ones.

            • 3. Re: Is it FMP or Apple that's the problem?
              taylorsharpe

              I have seen corrupt in a layout like this.  Try copying parts of the layout and see what happens.  Keep doing it until it crashes, then you know you have copied the corruption (or part of it).  Try to copy everything else. 

               

              In reality, whenever I have a corrupt layout, I don't want to keep it anymore.  So I rebuilt it manually. 

              • 4. Re: Is it FMP or Apple that's the problem?
                keywords

                Sounds very annoying, and requires much patience. To avoid having your new file crash as well when FMP crashes, I suggest you don't open it at the same time as you have your old file open. Use the process: open old file, copy stuff, if the copy process induces a crash, open source again, copy less/something else, if there is no crash close old file, open new file, paste.

                • 5. Re: Is it FMP or Apple that's the problem?
                  gdurniak

                  since it crashes on copy, you can't examine the Layout XML on the clipboard ( e.g. with Clip Manager )

                   

                  run a Consistency Check and a Recover, and check the log for any items "changed"

                   

                  also, try working with a different OS,  e.g. Windows

                   

                  greg