3 Replies Latest reply on Jan 10, 2013 12:05 PM by philmodjunk

    FM script crashes, but not while in the debugger

    miltenb_1

      Title

      FM script crashes, but not while in the debugger

      Post

           LS,
           I have a script that crashes when run. However, I doesn't crash if you run the script using the debugger. It crashes on MacOS X 10.8.2 and Windows ( any version ).

           If I place [show custom dialog] script steps between every script step, it runs fine.

            

           Update : It crashes. FM just quits with the resulting : filemaker unexpectedly quit. Send report ?

        • 1. Re: FM script crashes, but not while in the debugger
          Sorbsbuster

               Can you post the script?

               When you say the script 'crashes', what do you mean?  It hangs, goes into a ,n infinite loop, crashes Filemaker, doesn't give you the result you expect...?

          • 2. Re: FM script crashes, but not while in the debugger
            miltenb_1

                 I have started ripping out script steps. It seems that the 'restore page setup' script step causes the crash.

                 However, a second try still crashes FM.

                 the script :
                 go to layout
                 print[]
                 go to original layout

                 Not really complex i'd say.

            • 3. Re: FM script crashes, but not while in the debugger
              philmodjunk

                   Run a recover on the file and see if a recovered copy has the same issue. Not only could damage to your file cause the crash, but the crashes you have could damage your file.

                   Things to keep in mind about Recover:

                   While Recover almost always detects and fully corrects any problems with your file...

                     
              1.           The recovered copy may behave differently even if recover reports "no problems found".
              2.      
              3.           Recover does not detect all problems
              4.      
              5.           Recover doesn't always fix all problems correctly
              6.      
              7.           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.

                    

                   And here's a knowledgebase article that you may find useful: What to do when your file is corrupt (KB5421).