12 Replies Latest reply on Jul 5, 2010 8:49 AM by LSI-FileMaker-Developer

    FileMaker 11 just crashes way too much :(

    LSI-FileMaker-Developer

      Summary

      FileMaker 11 just crashes way too much :(

      Description of the issue

      Ever since upgrading from FileMaker 10 to 11, I've noticed a dramatic increase in crashes during development.  The crashes I'm experiencing always happen when double-clicking on a script step, specifically Set Field and Perform Script.  There have also been a few occasions where selecting Perform Script and then hitting the Specify… button on the bottom-right would cause a crash. The crashing has become so commonplace that I've gotten into the habit of saving my scripts before performing one of the actions listed above.  I've probably had around 25 crashes or so in the last month. I've been starting to submit the Apple crash reports in hopes that someone, somewhere, is letting FileMaker know that they have an unstable product, but for all I know I'm leaving food out for a stone idol. So I have a few questions:1)  When submitting those crash reports for third party programs like FileMaker, does Apple notify that third party?  I would imagine Apple can do little with programs that they don't control directly (ignoring the fact that FileMaker is owned by Apple).2)  Can we expect an 11.0v2 release?3)  Is anyone else experiencing an uptick in crashes since moving to version 11? Below is a truncated version of my latest crash report: Process:         FileMaker Pro [71600]
      Path:            /Applications/FileMaker Pro 11 Advanced/FileMaker Pro Advanced.app/Contents/MacOS/FileMaker Pro
      Identifier:      com.filemaker.client.advanced
      Version:         11.0.1 (11.0.1)
      Code Type:       X86 (Native)
      Parent Process:  launchd [683]

      Interval Since Last Report:          848011 sec
      Crashes Since Last Report:           1
      Per-App Interval Since Last Report:  803558 sec
      Per-App Crashes Since Last Report:   1

      Date/Time:       2010-06-22 15:14:11.874 -0500
      OS Version:      Mac OS X 10.5.8 (9L30)
      Report Version:  6
      Anonymous UUID:  B499411D-3DA1-4D2B-915F-905721DE53B8

      Exception Type:  EXC_BAD_ACCESS (SIGBUS)
      Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000200
      Crashed Thread:  0

      Thread 0 Crashed:
      0   com.filemaker.client.advanced      0x0017fad6 FMCatalogPopup::SetCatalog(Draco::DBCatalog*, bool) + 22
      1   com.filemaker.client.advanced      0x00136dbf CSpecifyFieldForScriptDlog::SetItems() + 79
      2   com.filemaker.client.advanced      0x00137a6f CSpecifyFieldForScriptDlog::OnInitDialog() + 31
      3   com.filemaker.client.advanced      0x0003656e CMacDialog::DoModal() + 414
      4   com.filemaker.client.advanced      0x00205755 CFMDialog::DoModal() + 101
      5   com.filemaker.client.advanced      0x00345d8c SaveVerbOptions_EnvRec::ReadCheckBox(Draco::ScriptStep::StepFlags, short) + 1340
      6   com.filemaker.client.advanced      0x00349668 SaveVerbOptions_EnvRec::SaveVerbOptions_Env(TVerbDlogTypeRec*, Draco::RefCountedObjPtr&, Draco::ScriptStep&, short) + 440
      7   com.filemaker.client.advanced      0x00342216 SCRIPTS_SaveVerbOptions(TVerbDlogTypeRec*, Draco::RefCountedObjPtr&, Draco::ScriptStep&, short) + 54
      8   com.filemaker.client.advanced      0x0033ae70 CEditScriptDlog::ApplyScriptOptions(short) + 272
      9   com.filemaker.client.advanced      0x0033b411 CEditScriptDlog::OnExecutionListDblClick(MacNMHDR*, long*) + 417
      10  com.filemaker.client.advanced      0x0002df69 CMacCmdTarget::OnCmdMsg(unsigned int, int, void*, MAC_CMDHANDLERINFO*) + 313
      11  com.filemaker.client.advanced      0x00032f77 XDialog::OnCmdMsg(unsigned int, int, void*, MAC_CMDHANDLERINFO*) + 87
      12  com.filemaker.client.advanced      0x004d7f40 -[CocoaDialog dblclickevent:] + 144
      13  com.apple.AppKit                   0x937eae8f -[NSApplication sendAction:to:from:] + 112
      14  com.apple.AppKit                   0x937eadcc -[NSControl sendAction:to:] + 108
      15  com.apple.AppKit                   0x93832ddf -[NSTableView _sendAction:to:row:column:] + 271
      16  com.apple.AppKit                   0x93831149 -[NSTableView mouseDown:] + 8228
      17  com.apple.AppKit                   0x937e7af7 -[NSWindow sendEvent:] + 5381
      18  com.filemaker.client.advanced      0x004d62c9 -[MFWindow sendEvent:] + 201
      19  com.apple.AppKit                   0x937b46a5 -[NSApplication sendEvent:] + 2939
      20  com.apple.AppKit                   0x93711fe7 -[NSApplication run] + 867
      21  com.filemaker.client.advanced      0x0002c10d CMacApp_Main + 413
      22  com.filemaker.client.advanced      0x00160dd3 main + 51
      23  com.filemaker.client.advanced      0x00003586 start + 54

      Thread 1:
      0   libSystem.B.dylib                  0x92fc644e __semwait_signal + 10
      1   ...filemaker.support.framework     0x027ad9dc Draco::Thread::Sleep(unsigned long) + 172
      2   ...filemaker.support.framework     0x027adddc Draco::TimerCheckThread::Main() + 252
      3   ...filemaker.support.framework     0x027aa0fe Draco::Thread::RunThread() + 46
      4   ...filemaker.support.framework     0x027ab3c8 Draco::Thread::ThreadUnixProc(void*) + 72
      5   libSystem.B.dylib                  0x92ff0155 _pthread_start + 321
      6   libSystem.B.dylib                  0x92ff0012 thread_start + 34

      Thread 2:
      0   libSystem.B.dylib                  0x92fc644e __semwait_signal + 10
      1   libSystem.B.dylib                  0x92ff0dcd pthread_cond_wait$UNIX2003 + 73
      2   ...filemaker.support.framework     0x027ac50f Draco::Semaphore::P(Draco::Thread*) + 159
      3   ...filemaker.support.framework     0x027ad125 Draco::MsgQ::GetMsg() + 69
      4   ...ilemaker.dbengine.framework     0x02928b90 Draco::HBEngine::HBEngineThread::Main() + 128
      5   ...filemaker.support.framework     0x027aa0fe Draco::Thread::RunThread() + 46
      6   ...filemaker.support.framework     0x027ab3c8 Draco::Thread::ThreadUnixProc(void*) + 72
      7   libSystem.B.dylib                  0x92ff0155 _pthread_start + 321
      8   libSystem.B.dylib                  0x92ff0012 thread_start + 34

      Thread 3:
      0   libSystem.B.dylib                  0x92fc644e __semwait_signal + 10
      1   libSystem.B.dylib                  0x92ff0dcd pthread_cond_wait$UNIX2003 + 73
      2   ...filemaker.support.framework     0x027ac50f Draco::Semaphore::P(Draco::Thread*) + 159
      3   ...filemaker.support.framework     0x027ad125 Draco::MsgQ::GetMsg() + 69
      4   ...ilemaker.dbengine.framework     0x02a20fc7 Draco::DBEngineThread::Main() + 135
      5   ...filemaker.support.framework     0x027aa0fe Draco::Thread::RunThread() + 46
      6   ...filemaker.support.framework     0x027ab3c8 Draco::Thread::ThreadUnixProc(void*) + 72
      7   libSystem.B.dylib                  0x92ff0155 _pthread_start + 321
      8   libSystem.B.dylib                  0x92ff0012 thread_start + 34

      Thread 4:
      0   libSystem.B.dylib                  0x92fc644e __semwait_signal + 10
      1   libSystem.B.dylib                  0x92ff0dcd pthread_cond_wait$UNIX2003 + 73
      2   ...filemaker.support.framework     0x027ac50f Draco::Semaphore::P(Draco::Thread*) + 159
      3   ...filemaker.support.framework     0x027ad125 Draco::MsgQ::GetMsg() + 69
      4   ...ilemaker.dbengine.framework     0x02a8a3a8 Draco::DBLockContinueThread::Main() + 648
      5   ...filemaker.support.framework     0x027aa0fe Draco::Thread::RunThread() + 46
      6   ...filemaker.support.framework     0x027ab3c8 Draco::Thread::ThreadUnixProc(void*) + 72
      7   libSystem.B.dylib                  0x92ff0155 _pthread_start + 321
      8   libSystem.B.dylib                  0x92ff0012 thread_start + 34

      Thread 5:
      0   libSystem.B.dylib                  0x92fc644e __semwait_signal + 10
      1   libSystem.B.dylib                  0x92ff0dcd pthread_cond_wait$UNIX2003 + 73
      2   libGLProgrammability.dylib         0x971b6b32 glvmDoWork + 162
      3   libSystem.B.dylib                  0x92ff0155 _pthread_start + 321
      4   libSystem.B.dylib                  0x92ff0012 thread_start + 34

      Thread 6:
      0   libSystem.B.dylib                  0x92fbf266 mach_msg_trap + 10
      1   libSystem.B.dylib                  0x92fc6a5c mach_msg + 72
      2   com.apple.CoreFoundation           0x92927e7e CFRunLoopRunSpecific + 1790
      3   com.apple.CoreFoundation           0x92928aa8 CFRunLoopRunInMode + 88
      4   com.apple.Foundation               0x97bf5520 +[NSURLConnection(NSURLConnectionReallyInternal) _resourceLoadLoop:] + 320
      5   com.apple.Foundation               0x97b91dfd -[NSThread main] + 45
      6   com.apple.Foundation               0x97b919a4 __NSThread__main__ + 308
      7   libSystem.B.dylib                  0x92ff0155 _pthread_start + 321
      8   libSystem.B.dylib                  0x92ff0012 thread_start + 34

      Thread 7:
      0   libSystem.B.dylib                  0x92fbf266 mach_msg_trap + 10
      1   libSystem.B.dylib                  0x92fc6a5c mach_msg + 72
      2   com.apple.CoreFoundation           0x92927e7e CFRunLoopRunSpecific + 1790
      3   com.apple.CoreFoundation           0x92928aa8 CFRunLoopRunInMode + 88
      4   com.apple.CFNetwork                0x90c77264 CFURLCacheWorkerThread(void*) + 388
      5   libSystem.B.dylib                  0x92ff0155 _pthread_start + 321
      6   libSystem.B.dylib                  0x92ff0012 thread_start + 34

      Thread 8:
      0   libSystem.B.dylib                  0x9300e6fa select$DARWIN_EXTSN + 10
      1   libSystem.B.dylib                  0x92ff0155 _pthread_start + 321
      2   libSystem.B.dylib                  0x92ff0012 thread_start + 34

      Thread 9:
      0   libSystem.B.dylib                  0x9300e6fa select$DARWIN_EXTSN + 10
      1   ...ilemaker.omniorb4.framework     0x0375fc82 omni::tcpEndpoint::AcceptAndMonitor(void (*)(void*, omni::giopConnection*), void*) + 136
      2   ...ilemaker.omniorb4.framework     0x036c43ff omni::giopRendezvouser::execute() + 159
      3   ...ilemaker.omniorb4.framework     0x036d5f28 omniAsyncWorker::real_run() + 334
      4   ...ilemaker.dbengine.framework     0x02972146 threadCreateInterceptor(omni::omniInterceptors::createThread_T::info_T&) + 22
      5   ...ilemaker.omniorb4.framework     0x036d6134 omniAsyncWorker::run(void*) + 50
      6   ...ilemaker.omniorb4.framework     0x0374ed0e omni_thread_wrapper + 160
      7   libSystem.B.dylib                  0x92ff0155 _pthread_start + 321
      8   libSystem.B.dylib                  0x92ff0012 thread_start + 34

      Thread 10:
      0   libSystem.B.dylib                  0x92fc644e __semwait_signal + 10
      1   libSystem.B.dylib                  0x930169f8 pthread_cond_timedwait$UNIX2003 + 72
      2   ...ilemaker.omniorb4.framework     0x0374dff5 omni_condition::timedwait(unsigned long, unsigned long) + 63
      3   ...ilemaker.omniorb4.framework     0x036cad43 omni::Scavenger::execute() + 179
      4   ...ilemaker.omniorb4.framework     0x036d5f28 omniAsyncWorker::real_run() + 334
      5   ...ilemaker.dbengine.framework     0x02972146 threadCreateInterceptor(omni::omniInterceptors::createThread_T::info_T&) + 22
      6   ...ilemaker.omniorb4.framework     0x036d6134 omniAsyncWorker::run(void*) + 50
      7   ...ilemaker.omniorb4.framework     0x0374ed0e omni_thread_wrapper + 160
      8   libSystem.B.dylib                  0x92ff0155 _pthread_start + 321
      9   libSystem.B.dylib                  0x92ff0012 thread_start + 34

      Thread 11:
      0   libSystem.B.dylib                  0x9300e74e recvfrom$UNIX2003 + 10
      1   ...ilemaker.omniorb4.framework     0x0375f509 omni::tcpConnection::Recv(void*, unsigned long, unsigned long, unsigned long) + 357
      2   ...ilemaker.omniorb4.framework     0x036ce76a omni::giopStream::inputMessage() + 336
      3   ...ilemaker.omniorb4.framework     0x036c2ff5 omni::giopImpl12::inputNewServerMessage(omni::giopStream*) + 71
      4   ...ilemaker.omniorb4.framework     0x036c3148 omni::giopImpl12::inputMessageBegin(omni::giopStream*, void (*)(omni::giopStream*)) + 174
      5   ...ilemaker.omniorb4.framework     0x036b6dc6 omni::GIOP_S::dispatcher() + 96
      6   ...ilemaker.omniorb4.framework     0x036d09f2 omni::giopWorker::real_execute() + 1406
      7   ...ilemaker.omniorb4.framework     0x036d0aaa omni::giopWorker::execute() + 50
      8   ...ilemaker.omniorb4.framework     0x036d5f28 omniAsyncWorker::real_run() + 334
      9   ...ilemaker.dbengine.framework     0x02972146 threadCreateInterceptor(omni::omniInterceptors::createThread_T::info_T&) + 22
      10  ...ilemaker.omniorb4.framework     0x036d6134 omniAsyncWorker::run(void*) + 50
      11  ...ilemaker.omniorb4.framework     0x0374ed0e omni_thread_wrapper + 160
      12  libSystem.B.dylib                  0x92ff0155 _pthread_start + 321
      13  libSystem.B.dylib                  0x92ff0012 thread_start + 34

      Thread 12:
      0   libSystem.B.dylib                  0x9300e6fa select$DARWIN_EXTSN + 10
      1   ...ilemaker.omniorb4.framework     0x0375be8e omni::tcpActiveCollection::Monitor(void (*)(void*, omni::giopConnection*), void*) + 42
      2   ...ilemaker.omniorb4.framework     0x036c4152 omni::giopMonitor::execute() + 74
      3   ...ilemaker.omniorb4.framework     0x036d5f28 omniAsyncWorker::real_run() + 334
      4   ...ilemaker.dbengine.framework     0x02972146 threadCreateInterceptor(omni::omniInterceptors::createThread_T::info_T&) + 22
      5   ...ilemaker.omniorb4.framework     0x036d6134 omniAsyncWorker::run(void*) + 50
      6   ...ilemaker.omniorb4.framework     0x0374ed0e omni_thread_wrapper + 160
      7   libSystem.B.dylib                  0x92ff0155 _pthread_start + 321
      8   libSystem.B.dylib                  0x92ff0012 thread_start + 34

      Thread 13:
      0   libSystem.B.dylib                  0x92fc644e __semwait_signal + 10
      1   libSystem.B.dylib                  0x92ff0dcd pthread_cond_wait$UNIX2003 + 73
      2   ...filemaker.support.framework     0x027ac50f Draco::Semaphore::P(Draco::Thread*) + 159
      3   ...filemaker.support.framework     0x027ac71a Draco::RepThread::RunThread() + 90
      4   ...filemaker.support.framework     0x027ab3c8 Draco::Thread::ThreadUnixProc(void*) + 72
      5   libSystem.B.dylib                  0x92ff0155 _pthread_start + 321
      6   libSystem.B.dylib                  0x92ff0012 thread_start + 34

      Thread 14:
      0   libSystem.B.dylib                  0x92fc644e __semwait_signal + 10
      1   libSystem.B.dylib                  0x92ff0dcd pthread_cond_wait$UNIX2003 + 73
      2   ...filemaker.support.framework     0x027ac50f Draco::Semaphore::P(Draco::Thread*) + 159
      3   ...filemaker.support.framework     0x027ac71a Draco::RepThread::RunThread() + 90
      4   ...filemaker.support.framework     0x027ab3c8 Draco::Thread::ThreadUnixProc(void*) + 72
      5   libSystem.B.dylib                  0x92ff0155 _pthread_start + 321
      6   libSystem.B.dylib                  0x92ff0012 thread_start + 34

      Thread 15:
      0   libSystem.B.dylib                  0x9300e74e recvfrom$UNIX2003 + 10
      1   ...ilemaker.omniorb4.framework     0x0375f509 omni::tcpConnection::Recv(void*, unsigned long, unsigned long, unsigned long) + 357
      2   ...ilemaker.omniorb4.framework     0x036ce76a omni::giopStream::inputMessage() + 336
      3   ...ilemaker.omniorb4.framework     0x036c2ff5 omni::giopImpl12::inputNewServerMessage(omni::giopStream*) + 71
      4   ...ilemaker.omniorb4.framework     0x036c3148 omni::giopImpl12::inputMessageBegin(omni::giopStream*, void (*)(omni::giopStream*)) + 174
      5   ...ilemaker.omniorb4.framework     0x036b6dc6 omni::GIOP_S::dispatcher() + 96
      6   ...ilemaker.omniorb4.framework     0x036d09f2 omni::giopWorker::real_execute() + 1406
      7   ...ilemaker.omniorb4.framework     0x036d0aaa omni::giopWorker::execute() + 50
      8   ...ilemaker.omniorb4.framework     0x036d5f28 omniAsyncWorker::real_run() + 334
      9   ...ilemaker.dbengine.framework     0x02972146 threadCreateInterceptor(omni::omniInterceptors::createThread_T::info_T&) + 22
      10  ...ilemaker.omniorb4.framework     0x036d6134 omniAsyncWorker::run(void*) + 50
      11  ...ilemaker.omniorb4.framework     0x0374ed0e omni_thread_wrapper + 160
      12  libSystem.B.dylib                  0x92ff0155 _pthread_start + 321
      13  libSystem.B.dylib                  0x92ff0012 thread_start + 34

      Thread 16:
      0   libSystem.B.dylib                  0x92fc644e __semwait_signal + 10
      1   libSystem.B.dylib                  0x92ff0dcd pthread_cond_wait$UNIX2003 + 73
      2   com.apple.JavaScriptCore           0x95dc5dff WTF::TCMalloc_PageHeap::scavengerThread() + 175
      3   com.apple.JavaScriptCore           0x95dc611f WTF::TCMalloc_PageHeap::runScavengerThread(void*) + 15
      4   libSystem.B.dylib                  0x92ff0155 _pthread_start + 321
      5   libSystem.B.dylib                  0x92ff0012 thread_start + 34

      Thread 17:
      0   libSystem.B.dylib                  0x92fc644e __semwait_signal + 10
      1   libSystem.B.dylib                  0x92ff0dcd pthread_cond_wait$UNIX2003 + 73
      2   com.apple.QuartzCore               0x95034a09 fe_fragment_thread + 54
      3   libSystem.B.dylib                  0x92ff0155 _pthread_start + 321
      4   libSystem.B.dylib                  0x92ff0012 thread_start + 34

      Thread 18:
      0   libSystem.B.dylib                  0x92fc644e __semwait_signal + 10
      1   libSystem.B.dylib                  0x92fc6216 usleep$UNIX2003 + 61
      2   com.apple.AppKit                   0x9377fbf1 -[NSUIHeartBeat _heartBeatThread:] + 2042
      3   com.apple.Foundation               0x97b91dfd -[NSThread main] + 45
      4   com.apple.Foundation               0x97b919a4 __NSThread__main__ + 308
      5   libSystem.B.dylib                  0x92ff0155 _pthread_start + 321
      6   libSystem.B.dylib                  0x92ff0012 thread_start + 34

      Thread 0 crashed with X86 Thread State (32-bit):
        eax: 0x00000001  ebx: 0x2668ce20  ecx: 0x25e86610  edx: 0x00000200
        edi: 0xbfffeb6c  esi: 0xbfffeb6c  ebp: 0xbfffe9c8  esp: 0xbfffe9a0
         ss: 0x0000001f  efl: 0x00210286  eip: 0x0017fad6   cs: 0x00000017
         ds: 0x0000001f   es: 0x0000001f   fs: 0x00000000   gs: 0x00000037
        cr2: 0x00000200

      Binary Images:
        

        • 1. Re: FileMaker 11 just crashes way too much :(
          ZoXo

          I have experience more crashing in version 11 than any other I have ever used.  So much so that I have totally

          rethought my development procedures.

           

          From now on I will do the following - as long as the file has not crashed I will continue to develop in it, but I will make

          periodic copies every 15 minutes or so as I wait for the next crash.

           

          When filemaker crashes, your file is now open to all kinds of ugly problems, even if you recover it, that you should only

          use for data.  I've had to rebuild several files now since I began using version 11, so all in all, the great features they

          added to help us developers has been totally offset by the fact the I am now having to periodically start sections of my development over again when the app crashes.

           

          And whoever said the progress was a good thing?  It seems that FileMaker is becoming less and less stable and things that have not worked since version 8.5 continue to still not work while us developers cry Henny Penny till we turn blue,

          and FileMaker seems to be just casually noting our discontent and not doing much about it.

           

          This reminds me of the stories I heard regarding Digidesign and the ProTools application and hardware.  From what I was told by an insider, digidesign support is only there to make you feel like you are being supported, while they quietly note the problems people are having.  This was done RATHER than have the application tested before releasing it, effectively saving them a substantial amount of money that should have been spent on testing.

           

          Is FileMaker doing the same thing to us - using the user base as a test environment, making us risk our hard work

          to catch all the bugs and issues that they then will 'attempt' to fix in upcoming versions or patches?

           

          If so, again I say, shame on you FileMaker.

           

          Shame on you for the issues I have brought to your attention that you still haven't fixed, and shame on you for releasing a product that on one hand gives us a powerful tool to build databases that inevitably become corrupt by the very tool we are using to build it.

           

          Hey, check out this new hammer, you can hammer a nail in half the time, but sometimes it will break the nail.

          Would you use this new hammer, or would you stick with one you know won't ever break the nail?

          • 2. Re: FileMaker 11 just crashes way too much :(
            philmodjunk

            This is the best place to report any trouble with filemaker. Not only do filemaker reps respond, but they engage in dialog with you to help isolate possible causes.

             

            Some context that may help them to help you:

             

            Do you see the frequent crashing on just one filemaker file or many different files? (that can rule out problems with your file)

             

            If available, can you install and run filemaker on a different machine and see if you still get frequent crashes? (that can rule out problems with your computer)

             

            • 3. Re: FileMaker 11 just crashes way too much :(
              mco_1

              As I have noted in another post, Filemaker 11 crashes every single time I try to print anything at all to a Konica Minolta printer. I appended my experience to the end of a long, seemingly unresolved, post. I hope 11 isn't a dud. As a non-profit group, investing in Filemaker Server 11 and a version 11 client was a big deal. Filemaker has never crashed before, like not even once! Through version 9, that is.

              • 4. Re: FileMaker 11 just crashes way too much :(
                LSI-FileMaker-Developer

                Thanks for the answers, Phil.

                 

                I spend 95% of my time developing on a single file, but the one definite pattern (in my case) is the fact that FileMaker 11 crashes more than version 10.  I did have the same types of crashes on another nearly identical computer (Mac OS X 10.5.8, FileMaker Pro Advanced 11.0v1).  It really truly does point to FileMaker 11 being buggy, nothing else.

                 

                I'm sorry I can't offer more specifics, but my original post is all I really know for a fact.

                 

                -Matt

                 

                p.s.  For others who are experiencing crashes, my condolences!

                • 5. Re: FileMaker 11 just crashes way too much :(
                  philmodjunk

                  " It really truly does point to FileMaker 11 being buggy, nothing else."

                  Except that we're not seeing a lot of bug reports here to that effect. I use XP with very stable results--which may explain the difference in experience, but I'd expect to see many more cases reported here if it were a problem with the Mac version of Filemaker 11.

                   

                  With all due respect to mco, I know you're frustrated, but the trouble you report is markedly different from HazMatt--so I can't class them together as being likely to have the same cause.

                   

                  File corruption can be a difficult issue to analyze. Some versions of filemaker will tolerate a problem with a file and appear to behave normally until you open the file with a new version or on a different platform. Since you spend 95% of your time in  a single file, I'd check that file out by recovering it and checking to see if any problems are found and if the recovered file is more stable than your development copy.

                   

                  PS. Best practice is to use recovered files only as a source of data to import into an uncorrupted backup clone--you never know if the recovered file is truly functional the way it should be.

                  • 6. Re: FileMaker 11 just crashes way too much :(
                    LSI-FileMaker-Developer

                    I will run a recovery on the file and see what pops up.  I don't maintain an uncorrupted backup clone, unfortunately.

                     

                    Thanks for the advice, and I'll try to keep this thread up-to-date on any new developments.

                     

                    -Matt

                    • 7. Re: FileMaker 11 just crashes way too much :(
                      mco_1

                      Ya, sorry for kinda coming in off topic!

                      • 8. Re: FileMaker 11 just crashes way too much :(
                        Steve Wright

                         


                        PhilModJunk wrote:

                        " It really truly does point to FileMaker 11 being buggy, nothing else."

                        Except that we're not seeing a lot of bug reports here to that effect. I use XP with very stable results--which may explain the difference in experience, but I'd expect to see many more cases reported here if it were a problem with the Mac version of Filemaker 11.

                         


                         

                        Im actually finding the mac version extremely stable, so much so.. I now do most of my work on it.

                         

                        I'm spending an awful lot of time developing / testing in FileMaker at the moment ( and have probably experienced 2 or 3 crashes since FM11 was released, but that could be anything.. Windows 7 is another story.

                         

                        Just my 2c.


                        • 9. Re: FileMaker 11 just crashes way too much :(
                          LSI-FileMaker-Developer

                          If you're not experiencing any problems on 10.6.3 (from your signature), I wonder if it's a Leopard 10.5 issue?  I'm not ruling out the possibility that it's an isolated problem on my system, but I wouldn't be surprised if FileMaker Inc. didn't test as thoroughly on 10.5.

                           

                          -Matt

                          • 10. Re: FileMaker 11 just crashes way too much :(
                            LSI-FileMaker-Developer

                            Well, lo and behold!  I have file corruption.  Here are the results I pulled from FileMaker Pro Advanced 11.0v1 a few days ago:

                            My DATA database file:

                            WARNING: problems were detected while recovering the database.  The recovered file should NOT be used going forward; copy only the most recent work from it into a backup copy of the original file.

                            File blocks: scanned and rebuilt 103543 block(s), dropped 0 invalid data block(s)

                            Schema: scanned fields and tables; some problems were found...

                              fields created to match record data: 5

                              field values deleted due to invalid ID or repetition: 0

                              records deleted due to invalid ID: 0

                            Structure: scanned; 4 item(s) modified

                            My INTERFACE database file:

                            WARNING: problems were detected while recovering the database.  The recovered file should NOT be used going forward; copy only the most recent work from it into a backup copy of the original file.

                            File blocks: scanned and rebuilt 9698 block(s), dropped 0 invalid data block(s)

                            Schema: scanned fields and tables; some problems were found...

                              fields created to match record data: 0

                              field values deleted due to invalid ID or repetition: 0

                              records deleted due to invalid ID: 0

                            Structure: scanned; 1 item(s) modified

                            I have no idea how to interpret these results, or whether or not they are directly related to my crashes I reported about earlier in this thread.  As an aside, I haven't experienced a FileMaker crash since I posted this thread.  So that's kind of strange.  I upgraded to 11.0v2 so we'll see how it goes.

                            -Matt

                            • 11. Re: FileMaker 11 just crashes way too much :(
                              Steve Wright

                              The x items modified may be nothing to worry about,  search the log for 'changed' and see if it refers to grouped objects being rebuilt  :  Copying grouped objects - causing "corruption"

                              However the fields created to match record data would concern me...
                              I would consider that a reason to revert to a backup for the "database" file anyway

                              • 12. Re: FileMaker 11 just crashes way too much :(
                                LSI-FileMaker-Developer

                                I read through that thread talking about grouped objects (fascinating how software has its demons, eh?) but my smpl_interface problem was something else:

                                0       Recovering: layout 'INV—Payment Details' (325)
                                8463       Deleted invalid object
                                8487       Reset table view
                                8476         This item changed
                                

                                The offending object was a 16x16 PNG graphic (obtained from the FM Graphics Pack, no less).  I deleted it in my source file, recreated it, ran a new recovery, and the problem was gone.  No problems reported.

                                As for the five 'recovered fields created to match data' problem, I'll have to try and track those down and come up with a solution.  As stated before, I don't have virgin copies to revert to, so I might try re-creating a good data file and exporting / importing the data.

                                This whole process of finding hidden, underlying bugs via the Recovery tool is pretty new to me, so this is a learning process.  Don't get me wrong, I've read about data corruption issues before and knew about certain 'best practices', but I've been too busy to pay too much attention to it.  As long as things seemed to work, I was happy.

                                Anyway, still no crashes, and I hope it stays that way.  I'll probably start a new thread for data corruption issues if I need help and only post back here for the original problem.

                                Thanks,

                                -Matt