4 Replies Latest reply on Jul 1, 2013 8:16 AM by tomasd

    Filemaker 12v4 Unexpectedly crash

    tomasd

      Summary

      Filemaker 12v4 Unexpectedly crash

      Product

      FileMaker Pro

      Version

      12v4

      Operating system version

      Windows XP / Windows7

      Description of the issue

      I have multiple hosted file solution. If I close the last window, Filemaker shows Open Recent files dialog and unexpectedly crash. The crash occurs in ntdll.

      Steps to reproduce the problem

      Close last file or exit application, after all files were open.

      Expected result

      Filemaker quit smoothly.

      Actual result

      Filemaker unexpected crash

      Exact text of any error message(s) that appear

      Filemaker has stopped unexpectedly...

      Configuration information

      FMServer 12v4 64bit (Windows 7 Pro 64bit)
      FMClient 12v4 (Windows XP)

      Workaround

      Wait 10+ seconds before closing last file. It doesnt matter which file it is.

      FMS12_-_Remote_Desktop_Connection_000068.png

        • 1. Re: Filemaker 12v4 Unexpectedly crash
          tomasd

               It looks like closing of files is too quick...and It doesn't matter which file is closed last. Sometimes if I wait 10+seconds before last file, the crash does not happen. But it isn't solution.

                This error is preventing me from use of Filemaker 12 in whole company. We are still using Filemaker 11.

          • 2. Re: Filemaker 12v4 Unexpectedly crash
            tomasd
                      (13e4.ec0): Access violation - code c0000005 (!!! second chance !!!)
                      SecondChance_av_AccessViolation
                       
                      Current time:
                      Debug session time: Mon Jun 17 15:29:56.852 2013 (UTC + 2:00)
                      System Uptime: 2 days 21:48:37.500
                      Process Uptime: 0 days 0:12:02.497
                        Kernel time: 0 days 0:00:26.629
                        User time: 0 days 0:01:28.577
                       
                 Call stack below ---
                  # ChildEBP RetAddr  Args to Child              
                 WARNING: Stack unwind information not available. Following frames may be wrong.
                 00 002af07c 771f8cd8 00000000 00000000 15fb7938 ntdll!RtlIntegerToUnicodeString+0x2fc
                 01 002af0a4 6e7235cf 15fb7938 00000000 002af0d8 ntdll!RtlIntegerToUnicodeString+0x20b
                 02 002af0b8 6e6a1c25 00000000 15fb78a0 6a5d2f6c Support!Draco::Mutex::Grab+0xf
                 03 002af0c4 6a5d2f6c 15fb7930 00000000 2cc1d6d0 Support!Draco::LockMutex::LockMutex+0x15
                 04 002af0e4 6a5cbf04 2cc1d6d0 2cc1d6d0 2cc1d6d0 DBEngine!Draco::DBCatalog::RemoveMemberReference+0x2c
                 05 002af100 6a72b648 2cc1d670 2cc1d6d0 002af128 DBEngine!Draco::DBCatalogMember::~DBCatalogMember+0x34
                 06 00000000 00000000 00000000 00000000 00000000 DBEngine!Draco::DBField::~DBField+0x68
                  
                 Here is DUMP file:
            • 3. Re: Filemaker 12v4 Unexpectedly crash
              tomasd

                   Very interesting thing happened today. When I deleted one table with 159 000 records, the issue has dissappeared. This table ('Participants') is connected to all other databases. Each record in main table (in every db) can have n participants. It works fine in Filemaker 11, but not in 12. I have to import records again.

              • 4. Re: Filemaker 12v4 Unexpectedly crash
                tomasd

                     Imported again (recovery didn't found any error), but the issue reappears. Maybe, the table full of records only highlights it. There are also some fm temp files left after the crash. I think that these should be deleted by Filemaker automatically. Something is broken during closing process in Filemaker 12v04.