4 Replies Latest reply on Mar 27, 2014 2:29 PM by BruceHerbach

    FileMaker crashes when it fails to open a database

    BruceHerbach

      Summary

      FileMaker crashes when it fails to open a database

      Product

      FileMaker Pro

      Version

      V 12 and V 13

      Operating system version

      OS X 10.8.5

      Description of the issue

      Trying to open a database from the recent list that has moved.  FileMaker reports that it can't find the database.  Click the OK button and a Crash report opens with the message "FileMaker Pro Advanced quit unexectedly"

      Steps to reproduce the problem

      Open and close a database
      Move the database
      Try to open the database from the recent list
      Dialog box opens,  click OK

      Expected result

      FileMaker will continue to operate normally

      Actual result

      Crash report opens

      Exact text of any error message(s) that appear

      VM Regions Near 0x50000020:
          mapped file            0000000021e71000-0000000021eb2000 [  260K] r--/rwx SM=COW  /Applications/FileMaker Pro 13 Advanced/FileMaker Pro Advanced.app/Contents/Resources/FM12DApp.icns
      -->
          MALLOC_TINY            0000000078e00000-0000000078f00000 [ 1024K] rw-/rwx SM=COW 

      Application Specific Information:
      objc_msgSend() selector name: release
      Java information:
      Exception type: Bus Error (0xa) at pc=0000000092dd0a87

      Java VM: Java HotSpot(TM) Client VM (20.65-b04-462 mixed mode macosx-x86)

      Current thread (00000000859ecc00):  JavaThread "Thread-1" daemon [_thread_in_native, id=-1400088024, stack(00000000bf725000,00000000bff25000)]
      Stack: [00000000bf725000,00000000bff25000]

      Java Threads: ( => current thread )
        0000000085a28400 JavaThread "Timer-0" daemon [_thread_blocked, id=-1336262656, stack(00000000b04a4000,00000000b05a4000)]
      =>00000000859ecc00 JavaThread "Thread-1" daemon [_thread_in_native, id=-1400088024, stack(00000000bf725000,00000000bff25000)]
        00000000843c3c00 JavaThread "Low Memory Detector" daemon [_thread_blocked, id=-1308844032, stack(00000000b1eca000,00000000b1fca000)]
        00000000843c2c00 JavaThread "C1 CompilerThread0" daemon [_thread_blocked, id=-1309900800, stack(00000000b1dc8000,00000000b1ec8000)]
        00000000843c1c00 JavaThread "Signal Dispatcher" daemon [_thread_blocked, id=-1310957568, stack(00000000b1cc6000,00000000b1dc6000)]
        00000000843c0c00 JavaThread "Surrogate Locker Thread (Concurrent GC)" daemon [_thread_blocked, id=-1312014336, stack(00000000b1bc4000,00000000b1cc4000)]
        00000000843bac00 JavaThread "Finalizer" daemon [_thread_blocked, id=-1313071104, stack(00000000b1ac2000,00000000b1bc2000)]
        00000000843b9c00 JavaThread "Reference Handler" daemon [_thread_blocked, id=-1314127872, stack(00000000b19c0000,00000000b1ac0000)]
      Other Threads:
        00000000843b7400 VMThread [stack: 00000000b18be000,00000000b19be000] [id=-1315184640]
        00000000843c5400 WatcherThread [stack: 00000000b1fcc000,00000000b20cc000] [id=-1307787264]

      VM state:not at safepoint (normal execution)
      VM Mutex/Monitor currently owned by a thread: None

      Heap
      par new generation   total 14784K, used 8289K [0000000015710000, 0000000016710000, 0000000016710000)
        eden space 13184K,  62% used [0000000015710000, 0000000015f284f0, 00000000163f0000)
        from space 1600K,   0% used [00000000163f0000, 00000000163f0000, 0000000016580000)
        to   space 1600K,   0% used [0000000016580000, 0000000016580000, 0000000016710000)
      concurrent mark-sweep generation total 49152K, used 0K [0000000016710000, 0000000019710000, 000000001b710000)
      concurrent-mark-sweep perm gen total 12288K, used 5780K [000000001b710000, 000000001c310000, 000000001f710000)

      Code Cache  [0000000013690000, 0000000013749000, 0000000015690000)
      total_blobs=281 nmethods=142 adapters=83 free_code_cache=32805120 largest_free_block=0

      Virtual Machine Arguments:
      JVM Args: -Xbootclasspath/a:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/../Resources/JavaPluginCocoa.bundle/Contents/Resources/Java/deploy.jar:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/../Resources/JavaPluginCocoa.bundle/Contents/Resources/Java/plugin.jar:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib/deploy.jar:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib/plugin.jar:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib/jaws.jar -Djava.ext.dirs=/System/Library/Java/Extensions:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib/ext:/Library/Java/Extensions -Dcom.apple.eawt.CocoaComponent.CompatibilityMode=false
      Java Command:
      Launcher Type: generic
      Physical Memory: Page Size = 4k, Total = 16384M, Free = 17592186043150M

      Configuration information

      Standard install of FileMaker Pro advanced.  There are some plugins.

      Workaround

      None

        • 1. Re: FileMaker crashes when it fails to open a database
          TSGal

               bherbac:

               Thank you for your post.

               I am unable to replicate the issue.  This is what I have done:

               1. In FileMaker Pro 12.0v5 on Mac OS X 10.8.5, I created a database file, TEST.fmp12, with one table, and two fields: ID (Number) and Name (Text).

               2. I created a second file, TEST2.fmp12, with one table, and two fields: ID (Number) and Address (Text)

               3. In TEST.fmp12, I created a relationship between TEST and TEST2 via the field ID.

               4. I added a portal into TEST2 showing the Address field.

               5. I closed TEST.fmp12 and TEST2.fmp12.

               6. I renamed TEST2.fmp12 to TEST3.fmp12

               7. I opened TEST.fmp12, and I get the message "The file "TEST2.fmp12" could not be opened.  (Not found)".  I click OK, the Open File window opens, I click Cancel, and TEST.fmp12 opens.

               8. I quit FileMaker Pro 12.0v5. launch FileMaker Pro 13.0v1, open TEST.fmp12, and I get the same message as in step #7 above.  After clicking Cancel, TEST.fmp12 opens successfully.

               Since the crash is happening to you on both FileMaker Pro 12.0v5 and FileMaker Pro 13.0v1, consider removing all plug-ins.  If this works, then add back one plug-in and try again.  Repeat until the offending plug-in is found.

               If after removing all plug-ins you still get a crash, what else can you tell me about your computing envinroment?

               TSGal
               FileMaker, Inc.

          • 2. Re: FileMaker crashes when it fails to open a database
            BruceHerbach

                 I removed the Dracoventions developer assistant plugin and this resolved the problem.  I was using version 2.67 of the plugin.  I reported this to them and asked about an update to the current version.

                 Thanks for looking into this.

            • 3. Re: FileMaker crashes when it fails to open a database
              TSGal

                   bherbac:

                   Sometimes, it isn't just one plug-in that causes the issue, but a combination of two plug-ins.  Therefore, remove all plug-ins except the Dracoventions developer assistant plug-in to verify.  If it works with just the Dracoventions plug-in installed, then install the others one at a time until it fails.

                   TSGal
                   FileMaker, Inc.

              • 4. Re: FileMaker crashes when it fails to open a database
                BruceHerbach

                     Hi,

                     In FileMaker 13  this was the only plugin there.  I'll test out 12 as suggested and get back to you.

                      

                     Regards

                     Bruce