1 2 3 Previous Next 36 Replies Latest reply on May 18, 2015 9:30 AM by TSGal

    FileMaker Server 13 Crash when processing new container images

    JohnDuncan

      Summary

      FileMaker Server 13 Crash when processing new container images

      Product

      FileMaker Server

      Version

      13.0v1

      Operating system version

      Mac OS X 10.9.1

      Description of the issue

      I am in the process of converting 10 containers in a base record to records in a related table.  The process loops through each record in the main table and for each container in each record it checks to see if there is anything in it and if there is it creates a new related record with the container contents.  The script does some more things than that but that is the primary function.  When running this script FileMaker Server 13 will crash part way through.  The problem does not appear to be related to a specific container content.  One time it crashed after 851 containers, another time after 970, and a third time after 2022.

      Steps to reproduce the problem

      I have reproduced the problem with both FM Pro 12.0v4 and 13.0v1 running on a Mac with 10.8.5.  To reproduce the problem would probably require running this script in this database.

      Expected result

      Should not crash

      Actual result

      Crashes after some variable period of time.

      Exact text of any error message(s) that appear

      No error messages are displayed on the client other than the message about the files no longer being available.  On the server a Crash Log file is created.  the top says:

      Process:         fmserverd [49530]
      Path:            /Library/FileMaker Server/*/fmserverd
      Identifier:      fmserverd
      Version:         ???
      Code Type:       X86-64 (Native)
      Parent Process:  launchd [1]
      Responsible:     fmserver_helperd [49453]
      User ID:         502

      Date/Time:       2013-12-21 13:02:26.213 -0500
      OS Version:      Mac OS X 10.9 (13A603)
      Report Version:  11
      Anonymous UUID:  B811380F-A24B-4B43-BEBB-7EE83434F12C


      Crashed Thread:  45

      Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
      Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000003000

      ------- AND THE THREAD 45 DUMP IS --------------

      Thread 45 Crashed:
      0   libsystem_platform.dylib           0x00007fff8eb8c050 _platform_memmove$VARIANT$Nehalem + 112
      1   com.filemaker.support.framework     0x0000000103ca8541 Draco::ByteBuffer::Get(char*, unsigned int, unsigned int) const + 359
      2   com.filemaker.support.framework     0x0000000103ca8aaf Draco::DataProviderGetBytesAtPositionCallback(void*, void*, long long, unsigned long) + 34
      3   com.apple.CoreGraphics             0x00007fff8a3524b3 CGAccessSessionGetBytes + 187
      4   com.apple.CoreGraphics             0x00007fff8a31e3ba CGDataProviderCopyData + 372
      5   com.apple.ImageIO.framework        0x00007fff8e643d38 CGImageReadCreateWithProvider + 229
      6   com.apple.ImageIO.framework        0x00007fff8e643bbf CGImageSourceCreateWithDataProvider + 202
      7   com.filemaker.support.framework     0x0000000103cee4aa Draco::Image2D::CreateImageFromData(Draco::ByteBuffer const*) + 40
      8   com.filemaker.support.framework     0x0000000103cee3e8 Draco::Image2D::Image2D(Draco::ByteBuffer const*, bool, Draco::QuadChar const&, Draco::UniversalPath const*, Draco::PhotoOrientation, Draco::PListMetadata*) + 304
      9   com.filemaker.support.framework     0x0000000103cee74e Draco::Image2D::LoadImage(Draco::ByteBuffer const&, Draco::QuadChar const&, Draco::UniversalPath const*, Draco::PhotoOrientation, Draco::PListMetadata*, bool) + 108
      10  com.filemaker.dbengine.framework     0x0000000102b82757 Draco::DBBinaryData::GetExactThumbnailOnHost(Draco::CoordSize*, bool, Draco::CacheItem**, bool, unsigned int&) const + 1935
      11  com.filemaker.dbengine.framework     0x0000000102d31713 Draco::RCDownloadThumbnail::Perform() + 609
      12  com.filemaker.dbengine.framework     0x0000000102d39fde Draco::RCNetworkStack::DispatchTransaction(Draco::RCConnection*, unsigned int, unsigned char*, unsigned int) + 1220
      13  com.filemaker.dbengine.framework     0x0000000102d39a1f RPO_i::Perform(unsigned int, char const*, unsigned int, OctetSeq&, OctetSeq_out) + 173
      14  com.filemaker.dbengine.framework     0x0000000102d35d19 _0RL_lcfn_07aabdf5dad7309d_70000000(omniCallDescriptor*, omniServant*) + 180
      15  com.filemaker.omniorb4.framework     0x00000001035e5d4f omniCallHandle::upcall(omniServant*, omniCallDescriptor&) + 1099
      16  com.filemaker.dbengine.framework     0x0000000102d36f01 _impl_RCFMP12::_dispatch(omniCallHandle&) + 1697
      17  com.filemaker.dbengine.framework     0x0000000102d37278 non-virtual thunk to _impl_RCFMP12::_dispatch(omniCallHandle&) + 16
      18  com.filemaker.omniorb4.framework     0x00000001036d75cf omni::omniOrbPOA::dispatch(omniCallHandle&, omniLocalIdentity*) + 715
      19  com.filemaker.omniorb4.framework     0x00000001036af7c2 omniLocalIdentity::dispatch(omniCallHandle&) + 94
      20  com.filemaker.omniorb4.framework     0x000000010363fc06 omni::GIOP_S::handleRequest() + 330
      21  com.filemaker.omniorb4.framework     0x000000010363f865 omni::GIOP_S::dispatcher() + 323
      22  com.filemaker.omniorb4.framework     0x000000010365cae6 omni::giopWorker::real_execute() + 1378
      23  com.filemaker.omniorb4.framework     0x000000010365ccd6 omni::giopWorker::execute() + 46
      24  com.filemaker.omniorb4.framework     0x00000001036621e7 omniAsyncWorker::real_run() + 657
      25  com.filemaker.dbengine.framework     0x0000000102a45056 Draco::threadCreateInterceptor(omni::omniInterceptors::createThread_T::info_T&) + 22
      26  com.filemaker.omniorb4.framework     0x0000000103662492 omniAsyncWorker::run(void*) + 46
      27  com.filemaker.omniorb4.framework     0x00000001036e6e59 omni_thread_wrapper + 148
      28  libsystem_pthread.dylib            0x00007fff8c042899 _pthread_body + 138
      29  libsystem_pthread.dylib            0x00007fff8c04272a _pthread_start + 137
      30  libsystem_pthread.dylib            0x00007fff8c046fc9 thread_start + 13

      Configuration information

      The server is running on a Mac Mini (5,2) with a Core i5 and 16GB of RAM and a stock 5400 RPM hard drive.   FM Server is allocated 2048MB cache.

      Workaround

      To work around the problem I have to convert the images in batches.

        • 1. Re: FileMaker Server 13 Crash when processing new container images
          philmodjunk

               While the crash could be due to a bug in FileMaker Server, it's not the only possibility.

               Figuring out why FileMaker is crashing can require some sleuthing to rule out possible issues.

               Basic diagnostic tests to perform when you get frequent crashes or “hangs”:

               Does the crash only occur with a specific file?
               Test by creating a small sample file and see if opening it and working with it also generates a crash. If it crashes too, the problem likely lies with the computer or it's installation of FileMaker. If it does not crash, it becomes more likely that there is a problem with the file.

               To check for possible problems on a specific computer, you may want to run a utility to check out the hard drive and also to check out the user accounts on that computer for possible problems.

               What is reported when you recover the file?
               The file could be damaged. Not only can file damage cause crashes, but the crashes (or forced quits after a "hang") can damage your file. You may need to test a recovered copy to see if it works without crashing.

               Things to keep in mind about Recover:

                 
          1.           Recover does not detect all problems
          2.      
          3.           Recover doesn't always fix all problems correctly
          4.      
          5.           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.


               Does it always crash when you are doing the same thing with your file?
               That may point to a specific layout, script, operation that interacts with your Operating system or other applications...
                

          • 2. Re: FileMaker Server 13 Crash when processing new container images
            JohnDuncan

                 Just had it happen again, this time with a totally different file.  This time the script was not creating new records but just exporting and re-importing the containers (to bring in Interactive PDFs).  Was processing about 9,000 records with containers in them.  Got to record 6672 and suddenly disconnected from FM Server 13.  Checked the server and it had crashed.  Here is an excerpt from the Crash log:

                 Process:         fmserverd [268]
                 Path:            /Library/FileMaker Server/*/fmserverd
                 Identifier:      fmserverd
                 Version:         ???
                 Code Type:       X86-64 (Native)
                 Parent Process:  launchd [1]
                 Responsible:     fmserver_helperd [77]
                 User ID:         502
                  
                 Date/Time:       2014-01-02 15:24:07.540 -0500
                 OS Version:      Mac OS X 10.9.1 (13B42)
                 Report Version:  11
                 Anonymous UUID:  B811380F-A24B-4B43-BEBB-7EE83434F12C
                  
                  
                 Crashed Thread:  44
                  
                 Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
                 Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
                  
                 VM Regions Near 0:
                 --> 
                     __TEXT                 000000010271e000-0000000102741000 [  140K] r-x/rwx SM=COW  /Library/FileMaker Server/*
                  
                  
                 --- and the Thread 44 details ---
                  
                      Thread 44 Crashed:
                      0   com.apple.CoreGraphics         0x00007fff8f617391 CGDataProviderCopyData + 331
                      1   com.apple.ImageIO.framework   0x00007fff8cfabd38 CGImageReadCreateWithProvider + 229
                      2   com.apple.ImageIO.framework   0x00007fff8cfabbbf CGImageSourceCreateWithDataProvider + 202
                      3   com.filemaker.support.framework 0x0000000103f4b4aa Draco::Image2D::CreateImageFromData(Draco::ByteBuffer const*) + 40
                      4   com.filemaker.support.framework 0x0000000103f4b3e8 Draco::Image2D::Image2D(Draco::ByteBuffer const*, bool, Draco::QuadChar const&, Draco::UniversalPath const*, Draco::PhotoOrientation, Draco::PListMetadata*) + 304
                      5   com.filemaker.support.framework 0x0000000103f4b74e Draco::Image2D::LoadImage(Draco::ByteBuffer const&, Draco::QuadChar const&, Draco::UniversalPath const*, Draco::PhotoOrientation, Draco::PListMetadata*, bool) + 108
                      6   com.filemaker.dbengine.framework 0x0000000102dd9757 Draco::DBBinaryData::GetExactThumbnailOnHost(Draco::CoordSize*, bool, Draco::CacheItem**, bool, unsigned int&) const + 1935
                      7   com.filemaker.dbengine.framework 0x0000000102f88713 Draco::RCDownloadThumbnail::Perform() + 609
                      8   com.filemaker.dbengine.framework 0x0000000102f90fde Draco::RCNetworkStack::DispatchTransaction(Draco::RCConnection*, unsigned int, unsigned char*, unsigned int) + 1220
                      9   com.filemaker.dbengine.framework 0x0000000102f90a1f RPO_i::Perform(unsigned int, char const*, unsigned int, OctetSeq&, OctetSeq_out) + 173
                      10  com.filemaker.dbengine.framework 0x0000000102f8cd19 _0RL_lcfn_07aabdf5dad7309d_70000000(omniCallDescriptor*, omniServant*) + 180
                      11  com.filemaker.omniorb4.framework 0x000000010383fd4f omniCallHandle::upcall(omniServant*, omniCallDescriptor&) + 1099
                      12  com.filemaker.dbengine.framework 0x0000000102f8df01 _impl_RCFMP12::_dispatch(omniCallHandle&) + 1697
                      13  com.filemaker.dbengine.framework 0x0000000102f8e278 non-virtual thunk to _impl_RCFMP12::_dispatch(omniCallHandle&) + 16
                      14  com.filemaker.omniorb4.framework 0x00000001039315cf omni::omniOrbPOA::dispatch(omniCallHandle&, omniLocalIdentity*) + 715
                      15  com.filemaker.omniorb4.framework 0x00000001039097c2 omniLocalIdentity::dispatch(omniCallHandle&) + 94
                      16  com.filemaker.omniorb4.framework 0x0000000103899c06 omni::GIOP_S::handleRequest() + 330
                      17  com.filemaker.omniorb4.framework 0x0000000103899865 omni::GIOP_S::dispatcher() + 323
                      18  com.filemaker.omniorb4.framework 0x00000001038b6ae6 omni::giopWorker::real_execute() + 1378
                      19  com.filemaker.omniorb4.framework 0x00000001038b6cd6 omni::giopWorker::execute() + 46
                      20  com.filemaker.omniorb4.framework 0x00000001038bc1e7 omniAsyncWorker::real_run() + 657
                      21  com.filemaker.dbengine.framework 0x0000000102c9c056 Draco::threadCreateInterceptor(omni::omniInterceptors::createThread_T::info_T&) + 22
                      22  com.filemaker.omniorb4.framework 0x00000001038bc492 omniAsyncWorker::run(void*) + 46
                      23  com.filemaker.omniorb4.framework 0x0000000103940e59 omni_thread_wrapper + 148
                      24  libsystem_pthread.dylib       0x00007fff8aa3e899 _pthread_body + 138
                      25  libsystem_pthread.dylib       0x00007fff8aa3e72a _pthread_start + 137
                      26  libsystem_pthread.dylib       0x00007fff8aa42fc9 thread_start + 13
                       

                  

                  

            • 3. Re: FileMaker Server 13 Crash when processing new container images
              TSGal

                   John Duncan:

                   Thank you for your posts.

                   There are some issues with Adobe Reader and Mavericks.  First check to see if you have either of the Adobe browser plugins for Safari installed: AdobePDFViewerNPAPI.plugin and AdobePDFViewer.plugin.  If so, remove them from /Library/Internet Plug-ins and relaunch FileMaker Pro.  Also, set PDF files to open under Apple's Preview application.

                   For more information, see the forum thread at:

              Records with a PDF file linked to an active container field cause FMP 12 to crash in OS 10.9

                   Let me know if you continue to run into difficulty.

                   TSGal
                   FileMaker, Inc.

              • 4. Re: FileMaker Server 13 Crash when processing new container images
                JohnDuncan

                     No Adobe Internet Plug-Ins installed on either client machine (OS X 10.8.5) or server (OS X 10.9.1).  PDF Files on both machines were already set to open with Preview.

                     It crashed 2 more times since my last posting earlier today.  The last time I watched the real memory on fmserverd gradually climbing as the records were being processed.  It started out at 1.78 GB and had climbed to 2.23 GB the last time I looked before it crashed again.

                • 5. Re: FileMaker Server 13 Crash when processing new container images
                  TSGal

                       John Duncan:

                       Thank you for the additional information.

                       Please send in a crash report file as well as your event logs.  Check your Inbox at the top of this page for instructions where to send the files.

                       TSGal
                       FileMaker, Inc.

                  • 6. Re: FileMaker Server 13 Crash when processing new container images
                    jdxxs

                         I have been experiencing consistent crashes when moving backwards and forwards between records with container fields in Filemaker Pro 13 on a Mac with Mavericks. The fields contain pdf files. Just moving between the records is enough to cause the crash.

                         As suggested above, I removed the two plug-in files and have not experienced a crash since.

                         The functionality of working with the pdf files is lost - such as being able to email the contained file - but, at least, it shows that this is the source of the problem.

                         Look forward to a solution so that I can regain functionality.

                         Jeff

                    • 7. Re: FileMaker Server 13 Crash when processing new container images
                      JohnDuncan

                           Problem occurred again with yet another client solution.  This one is using internally stored containers where the others were using remote containers.  I tried to follow TSGal instructions on how to upload the logs and crash log but didn't find the link in my inbox on where to send them.  Please re-send the information on where to upload the files

                      • 8. Re: FileMaker Server 13 Crash when processing new container images
                        mechai

                             I have the same issue with FM Server crashing on my new Mac Pro with Mavericks.

                             How shall I send in the crash log?

                             Also I am not using any Adobe PDF viewer. And the viewer should be client issue, not server side control right. 

                        • 9. Re: FileMaker Server 13 Crash when processing new container images
                          TSGal

                               John Duncan:

                               Check your Inbox again at the top of this page.  The instructions have been sent again.

                               TSGal
                               FileMaker, Inc.

                          • 10. Re: FileMaker Server 13 Crash when processing new container images
                            TSGal

                                 mech:

                                 Thank you for your post and screen shot.

                                 Check your Inbox for instructions where to send the crash report.

                                 TSGal
                                 FileMaker, Inc.

                            • 11. Re: FileMaker Server 13 Crash when processing new container images
                              TSGal

                                   John Duncan:

                                   I received your crash report and log files.  Thank you.

                                   I have sent them to Development and Testing for review.  I will keep you updated when I receive feedback.

                                   TSGal
                                   FileMaker, Inc.

                              • 12. Re: FileMaker Server 13 Crash when processing new container images
                                TSGal

                                     mech:

                                     I received your files.  Thank you.

                                     The files have been sent to Development and Testing for review.

                                     TSGal
                                     FileMaker, Inc.

                                • 13. Re: FileMaker Server 13 Crash when processing new container images
                                  mechai

                                       Any update so far on the crash inspection? I have been daily crash ever since. It is getting tedious to every day serve clients and need to restart daily :(

                                        

                                        

                                  • 14. Re: FileMaker Server 13 Crash when processing new container images
                                    TSGal

                                         mech:

                                         Testing and Development are still working with your files.  Testing would also like to see your solution to better understand why this is happening.  Send a copy of your file to the information given to you in the private message.

                                         TSGal
                                         FileMaker, Inc.

                                    1 2 3 Previous Next