12 Replies Latest reply on Jun 18, 2015 9:35 AM by Benjamin Fehr

    Filemaker 14 Crashes Periodically

    AnnKrause

      Summary

      Filemaker 14 Crashes Periodically

      Product

      FileMaker Pro

      Version

      14

      Operating system version

      OS X 10.10.3

      Description of the issue

      We have been running a POS system with Filemaker 13 and just upgraded to 14. When we run a credit card using 360 works plastic plugin, sometimes Filemaker crashes after the transaction is complete. We took out the lines of code that run the plugin the try to isolate the problem and the problem still exists. Filemaker does not crash every time we run a credit card, but it does happen frequently. It seems to completely finish the script before the program crashes.

      Steps to reproduce the problem

      Process a credit card in Filemaker 14.

      Expected result

      Filemaker to continue running after transaction.

      Actual result

      Filmaker crashes after script completes.

      Exact text of any error message(s) that appear

      Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
      Exception Codes:       EXC_I386_GPFLT

      Configuration information

      Unknown

      Workaround

      None found so far.

        • 1. Re: Filemaker 14 Crashes Periodically
          Benjamin Fehr

          a possible "Voodoo" workaround:

          set a Pause (0,5 seconds) right after the 360Works script step.

          • 2. Re: Filemaker 14 Crashes Periodically
            AnnKrause

            Thanks for the idea. We tried this and we are still having the same problem. If you have any other ideas we will try anything. Thank you.

            • 3. Re: Filemaker 14 Crashes Periodically
              TSGal

              Ann Krause:

              Thank you for your post.

              Please post the header of the crash report along with the crashed thread.  This will give me an idea what part of FileMaker Pro is crashing.

              TSGal
              FileMaker, Inc.

              • 4. Re: Filemaker 14 Crashes Periodically
                AnnKrause

                After a few hours of trial and error, we found that a swiped credit card seems to cause the problem. If we copy and paste the swiped data into the field, the error does not happen. We changed the program to put the swiped data into a field and then use a button to separate track 1 and 2, and then run the credit card with 360 works. Before when a card was swiped the data would go into a field. After parsing the field for two question marks the program would automatically separate the two tracks and run the card. This method worked in filemaker 13, but does not work in 14 and we are not sure why? If you have any suggestions for this situation we would appreciate it.

                • 5. Re: Filemaker 14 Crashes Periodically
                  philmodjunk

                  It definitely should not cause a crash. A more detailed description of how you have set up your system to handle the Mag Strip Reader data may provide a clue.

                  That crash report header that you were asked to provide could also help.

                  • 6. Re: Filemaker 14 Crashes Periodically
                    AnnKrause

                    Crash Report:

                    Process:               FileMaker Pro [397]
                    Path:                  /Applications/FileMaker Pro 14/FileMaker Pro.app/Contents/MacOS/FileMaker Pro
                    Identifier:            com.filemaker.client.pro12
                    Version:               14.0.1 (14.0.1)
                    Code Type:             X86-64 (Native)
                    Parent Process:        ??? [1]
                    Responsible:           FileMaker Pro [397]
                    User ID:               501

                    Date/Time:             2015-05-29 13:47:31.445 -0400
                    OS Version:            Mac OS X 10.10.3 (14D136)
                    Report Version:        11
                    Anonymous UUID:        BC3B0830-4446-1992-F780-DDC54C50966C


                    Time Awake Since Boot: 24000 seconds

                    Crashed Thread:        0  Dispatch queue: com.apple.main-thread

                    Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
                    Exception Codes:       EXC_I386_GPFLT

                     

                     

                     

                    ** This is the code we are using the process credit cards **

                    Swipe Card Script

                    # Retrieve Track 1 from Swiped Card
                    Set Field [CCSettings::CC Track 1 ; Middle ( Credit Cards::CC Swipe ; Position ( Credit Cards::CC Swipe ; "%" ; 1 ; 1 ) + 1 ; Position ( Credit Cards::CC Swipe ; "?" ; 1 ;1 ) - 2)]

                    # Retrieve CC# from Swiped Card
                    Set Field [CCSettings::CC Number ;  Middle ( Credit Cards::CC Swipe ; Position ( Credit Cards::CC Swipe ; "B" ; 1 ; 1 ) + 1 ; Position ( Credit Cards::CC Swipe ; "^" ; 1 ;1 ) - 2)]

                    # Retrieve First Name and then whole Name from Swiped Data
                    Set Field [Credit Cards::CC CustFirst Name ; Middle ( Credit Cards::CC Swipe ; Position ( Credit Cards::CC Swipe ; "/" ; 1 ; 1 ) + 1 ; Position ( Credit Cards::CC Swipe ; "^" ; 1 ;2))]

                    Set Field [CCSettings::CC CustName ;
                    Trim(Middle (Credit Cards::CC CustFirst Name ; 1; Position ( Credit Cards::CC CustFirst Name ; "^" ; 1 ; 1 ) - 1))

                    & " " &

                    Trim(Middle (Credit Cards::CC Swipe ; Position ( Credit Cards::CC Swipe ; "^" ; 1 ; 1 ) + 1; Position ( Credit Cards::CC Swipe ; "/" ; 1 ; 1 )  - Position ( Credit Cards::CC Swipe ; "^" ; 1 ; 1 ) - 1))

                    #   Retrieve Exp Date from Swiped Data
                    Set Field [CCSettings::CC ExpDate ;
                    Right ( Middle ( Credit Cards::CC Swipe ; Position ( Credit Cards::CC Swipe ; "^" ; 1 ; 2 ) +1 ; 4 ) ; 2 )

                    &

                    Left ( Middle ( Credit Cards::CC Swipe ; Position ( Credit Cards::CC Swipe ; "^" ; 1 ; 2 ) +1 ; 4 ) ; 2 )


                    # Set the Card Type
                    Set Field [CCSettings::CC Type ;
                    If ( Left ( CCSettings::CC Number ; 1 ) = 3 ; "AMEX" ;
                            If ( Left ( CCSettings::CC Number ; 1 ) = 4 ; "MasterCard/Visa" ;
                            If ( Left ( CCSettings::CC Number ; 1 ) = 5 ; "MasterCard/Visa" ;
                            If ( Left ( CCSettings::CC Number ; 1 ) = 6 ; "Discover" ; "" ) ) ) )

                    Perform Script [ “CC Process”]

                     

                     


                    Process Credit Card Script

                    # Set 1 for test mode 0 for real mode
                    Set Field [ CCSettings::g_text ; CCSetTestMode(0)]

                    # Set which processing gateway to use
                    Set Field [ CCSettings::g_text ; CCSetGateway( "Authorize.net" ; “cardPresent=true”)]
                    Set Field [ CCSettings::g_Merchant Acct ; “xxxxxxxx”]
                    Set Field [ CCSettings::g_Transaction Key ; “xxxxxxxx”]

                    # Run the Charge
                    Set Field [ CCSettings::CC Trans Num] ;
                    CCProcessPayment (CCProcessPayment(
                    CCSettings::g_merchant acct ;
                    CCSettings::g_transaction key ;
                    Transaction::Total Due ;
                    "";
                    "";
                    "track1=" & CCSettings::CC Track 1;
                    "invoiceNumber=" & Transaction::_Trans ID;
                    "chargeDescription="  & Transaction::Register Name;
                    "authDeviceType=Unattended_Terminal";
                    "firstName=" & CCSettings::CC CustName
                    )]

                    Set Field [ CCSettings::g_Processing ;
                    If ( CCSettings::CC Trans Num = "ERROR" ;
                    "The transaction failed because of an error: " & CCLastError;
                    "Transaction succeeded"  )]

                    • 7. Re: Filemaker 14 Crashes Periodically
                      TSGal

                      Ann Krause:

                      I see the header of the crash report, but not the thread that crashed (thread 0).  Please post the entire Thread 0.

                      You mentioned the script completes, but can you confirm the CCSettings::g_Processing field is updated correctly ("Transaction succeeded")?

                      TSGal
                      FileMaker, Inc.

                      • 8. Re: Filemaker 14 Crashes Periodically
                        AnnKrause

                        The script completes and the transaction is successful. The credit card processes successfully as well. Once the credit card has processed and all the scripts have completed, filemaker crashes.

                        Here is the rest of the crash report through the end of tread 0:

                        Process:               FileMaker Pro [397]
                        Path:                  /Applications/FileMaker Pro 14/FileMaker Pro.app/Contents/MacOS/FileMaker Pro
                        Identifier:            com.filemaker.client.pro12
                        Version:               14.0.1 (14.0.1)
                        Code Type:             X86-64 (Native)
                        Parent Process:        ??? [1]
                        Responsible:           FileMaker Pro [397]
                        User ID:               501

                        Date/Time:             2015-05-29 13:47:31.445 -0400
                        OS Version:            Mac OS X 10.10.3 (14D136)
                        Report Version:        11
                        Anonymous UUID:        BC3B0830-4446-1992-F780-DDC54C50966C


                        Time Awake Since Boot: 24000 seconds

                        Crashed Thread:        0  Dispatch queue: com.apple.main-thread

                        Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
                        Exception Codes:       EXC_I386_GPFLT

                        Application Specific Information:
                        objc_msgSend() selector name: release
                        Java information:
                         Exception type: Bus Error (0xa) at pc=7fff909f20d7
                         
                         Java VM: Java HotSpot(TM) 64-Bit Server VM (20.65-b04-466.1 mixed mode macosx-amd64)
                         
                        Current thread (7fe2390a6800):  JavaThread "Thread-1" daemon [_thread_in_native, id=2069218048, stack(7fff593f7000,7fff59bf7000)]
                        Stack: [7fff593f7000,7fff59bf7000]
                         
                        Java Threads: ( => current thread )
                          7fe239b72800 JavaThread "Keep-Alive-Timer" daemon [_thread_blocked, id=200228864, stack(10bdf4000,10bef4000)]
                          7fe23a0e7000 JavaThread "LicensePlugin KeepaliveThread 18/a5578f3f-4856-4232-a86d-80791a9ec065" daemon [_thread_blocked, id=467697664, stack(11bd08000,11be08000)]
                          7fe2399ac000 JavaThread "Timer-0" daemon [_thread_blocked, id=269897728, stack(110065000,110165000)]
                        =>7fe2390a6800 JavaThread "Thread-1" daemon [_thread_in_native, id=2069218048, stack(7fff593f7000,7fff59bf7000)]
                          7fe239853800 JavaThread "Low Memory Detector" daemon [_thread_blocked, id=398430208, stack(117af9000,117bf9000)]
                          7fe239852800 JavaThread "C2 CompilerThread1" daemon [_thread_blocked, id=397369344, stack(1179f6000,117af6000)]
                          7fe23909c000 JavaThread "C2 CompilerThread0" daemon [_thread_blocked, id=396308480, stack(1178f3000,1179f3000)]
                          7fe23909b800 JavaThread "Signal Dispatcher" daemon [_thread_blocked, id=395247616, stack(1177f0000,1178f0000)]
                          7fe23909a800 JavaThread "Surrogate Locker Thread (Concurrent GC)" daemon [_thread_blocked, id=394186752, stack(1176ed000,1177ed000)]
                          7fe239852000 JavaThread "Finalizer" daemon [_thread_blocked, id=393125888, stack(1175ea000,1176ea000)]
                          7fe239080800 JavaThread "Reference Handler" daemon [_thread_blocked, id=392065024, stack(1174e7000,1175e7000)]
                        Other Threads:
                          7fe239851000 VMThread [stack: 1173e4000,1174e4000] [id=391004160]
                          7fe2390a5800 WatcherThread [stack: 117bfc000,117cfc000] [id=399491072]
                         
                        VM state:not at safepoint (normal execution)
                        VM Mutex/Monitor currently owned by a thread: None
                         
                        Heap
                         par new generation   total 19136K, used 7114K [7f3000000, 7f44c0000, 7f44c0000)
                          eden space 17024K,  29% used [7f3000000, 7f34e2ac0, 7f40a0000)
                          from space 2112K, 100% used [7f40a0000, 7f42b0000, 7f42b0000)
                          to   space 2112K,   0% used [7f42b0000, 7f42b0000, 7f44c0000)
                         concurrent mark-sweep generation total 63872K, used 3172K [7f44c0000, 7f8320000, 7fae00000)
                         concurrent-mark-sweep perm gen total 21248K, used 12123K [7fae00000, 7fc2c0000, 800000000)
                         
                        Code Cache  [1107a8000, 110a19000, 1137a8000)
                         total_blobs=430 nmethods=140 adapters=252 free_code_cache=49541504 largest_free_block=16576
                         
                        Virtual Machine Arguments:
                        JVM Args: -Djava.net.preferIPv4Stack=true -Djsse.enableSNIExtension=false -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:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/jre/lib/ext:/Library/Java/Extensions -Dcom.apple.eawt.CocoaComponent.CompatibilityMode=false
                        Java Command: <unknown>
                        Launcher Type: generic
                        Physical Memory: Page Size = 4k, Total = 4096M, Free = 1081M
                         

                        Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
                        0   libobjc.A.dylib                   0x00007fff909f20d7 objc_msgSend + 23
                        1   com.apple.AppKit                  0x00007fff8f21111b -[NSWindow _reallySendEvent:isDelayedEvent:] + 5452
                        2   com.apple.AppKit                  0x00007fff8eba2d76 -[NSWindow sendEvent:] + 470
                        3   com.filemaker.client.pro12        0x00000001062c013c -[FMDocWindowCocoa sendEvent:] + 877
                        4   com.apple.AppKit                  0x00007fff8eb9f9b1 -[NSApplication sendEvent:] + 4199
                        5   com.filemaker.client.pro12        0x000000010600dc8e -[FMCocoaApplication sendEvent:] + 328
                        6   com.apple.AppKit                  0x00007fff8eac8c68 -[NSApplication run] + 711
                        7   com.filemaker.client.pro12        0x000000010600de90 CMacApp_Main + 501
                        8   com.filemaker.client.pro12        0x00000001060cd8a5 main + 66
                        9   libdyld.dylib                     0x00007fff8ab485c9 start + 1

                        • 9. Re: Filemaker 14 Crashes Periodically
                          TSGal

                          Ann Krause:

                          Thank you for the crashed thread, although the ten lines don't provide enough information to determine a cause of the crash.

                          What other applications are running at the time of the crash?  If you quit out of all other applications, do you still crash?

                          How much RAM exists in the machine?

                          Is it only the one script that produces the crash?  If so, create a new script (do not duplicate the existing script) and add each line and stop before the final transaction.  Run the new script.  Does it crash?

                          Any other information you can provide about your computing environment may be helpful.

                          TSGal
                          FileMaker, Inc.

                          • 10. Re: Filemaker 14 Crashes Periodically
                            AnnKrause


                            Comment:    
                            Ann Krause:

                            Thank you for the crashed thread, although the ten lines don't provide enough information to determine a cause of the crash.

                            What other applications are running at the time of the crash?  If you quit out of all other applications, do you still crash?

                            No other applications were open when filemaker crashed.

                            How much RAM exists in the machine?

                            This machine has 4GB of RAM

                            Is it only the one script that produces the crash?  If so, create a new script (do not duplicate the existing script) and add each line and stop before the final transaction.  Run the new script.  Does it crash?

                            We will try this when we have a chance

                            Any other information you can provide about your computing environment may be helpful.
                             

                            We are running filemaker13 server on about 12 computers. We also operate a second location with one computer using filemaker13 client. We want to upgrade to filemaker14 and have set up one computer at out main location with 14 client so that we will know it works before we send it to our other location. This is the machine that we are having the issue with. All of the other machines using version 13 from the server have no problems.

                             

                            • 11. Re: Filemaker 14 Crashes Periodically
                              TSGal

                              Ann Krause:

                              Reading through all of your posts again, I notice you are using 360Works plug-in.  Are you using the same plug-in for both FileMaker Pro 13 and FileMaker Pro 14?  I mention it because FileMaker Pro 13 is 32-bit and FileMaker Pro 14 is 64-bit, and the 32-bit plug-in may not work with FileMaker Pro 14.  Have you contacted 360Works to ensure the plug-in is compatible with FileMaker Pro 14?

                              TSGal
                              FileMaker, Inc.

                              • 12. Re: Filemaker 14 Crashes Periodically
                                Benjamin Fehr

                                Ann Kraus:

                                On Mac, you can click on the FMPA14 App, click cmd / i (get Info) and set the Option "Run in 32-bit Mode" for testing FMP14 in 32-bit Mode.