5 Replies Latest reply on Jul 28, 2016 7:58 AM by michaelp@alchemy

    Print Setup script step transferred from 14 to 15 caused crash

    michaelp@alchemy

      Product and version: FM Pro Adv 14.0.6->FM Pro Adv 15.0.1.119

      OS and version: OS X Yosemite, v 10.10.5

      Hardware: Mac Mini, 2.66 GHz Intel Core 2, 8GB RAM

      Description: A script created in 14, before 15 was released, used the Print Setup step to change the page orientation for a report.  A new file was created based on that file and opened in 15.  When the script was called, it crashed 15 completely.  When using the script debug

      How to replicate:

      Workaround:

       

       

        • 1. Re: Print Setup script step transferred from 14 to 15 caused crash
          TSGal

          michaelp:

           

          Thank you for your post.

           

          Please post the crash report, up to and including the crashed thread.  This may help provide why FileMaker Pro 15 crashed.

           

          Re-create the script (do not duplicate the existing script) and execute.  Does FileMaker Pro still crash?  I am trying to determine if the script is damaged or if a certain set of script steps caused the crash.

           

          TSGal

          FileMaker, Inc.

          • 2. Re: Print Setup script step transferred from 14 to 15 caused crash
            michaelp@alchemy

            It happened several times yesterday when it occurred, but since we solved it I haven’t been able to reproduce it, and I did not save the crash report at the time.  I do remember it referenced main thread 0 as where the problem occurred, but I don’t remember the details.  I’ve unsuccessfully tried to reproduce it in sample files and in the files it came from.  The only thing I haven’t tried in this vein is duplicating the entire origin file again.  The origin was a template which got duplicated and then renamed as a new base file for a solution, so if something went wrong in the duplication I supposed that could contribute.  The script itself also ran properly to a point, it successfully called a sub script and performed some other script steps, but failed if we allowed it to get to the Print Setup script step.

             

            When we recreated the script in 15 without duplication the new script ran fine in 14 and 15.

             

             

            Michael Primrose

            Alchemy Consulting Group, LLC

            FileMaker  13 & 14 Certified Developer

            FileMaker Business Alliance Platinum Member

            http://www.alchemyg.com <http://www.alchemyg.com/> - 888-663-6382

            • 3. Re: Print Setup script step transferred from 14 to 15 caused crash
              michaelp@alchemy

              So we’ve run across the same bug again, did additional testing, and this is what we found:

               

              1) it’s not related to the print setup script step, but rather earlier in the process

              2) it seems to be caused by entering find mode immediately before go to layout

              3) it does not happen when stepping through with script debugger

              4) it does not happen if you go to layout first, then enter find mode

              5) it does not happen if you put a 1 second pause in between enter find mode and go to layout

              6) it has no relation to anything on the layout, it happens with filled or empty layouts

              7) it doubtfully has any relation to the number of records because the destination layout TO only has 11 records currently

              8) it is not caused by a corrupted file that needed recovery, it behaved the same both pre- and post-recovery

              9) it only happens when the script is run in FM15, FM14 does not crash

               

              Also find a copy of one of the crash logs below.

               

              Process:               FileMaker Pro [300]

              Path:                  /Applications/FileMaker Pro 15 Advanced/FileMaker Pro Advanced 15.app/Contents/MacOS/FileMaker Pro

              Identifier:            com.filemaker.client.advanced12

              Version:               15.0.1 (15.0.1)

              Code Type:             X86-64 (Native)

              Parent Process:        ??? [1]

              Responsible:           FileMaker Pro [300]

              User ID:               503

               

              Date/Time:             2016-07-27 08:20:11.243 -0700

              OS Version:            Mac OS X 10.10.5 (14F1909)

              Report Version:        11

              Anonymous UUID:        BA830138-0F5E-038C-83B3-B73AF2B475B4

               

               

              Time Awake Since Boot: 1500 seconds

               

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

               

              Exception Type:        EXC_BAD_ACCESS (SIGSEGV)

              Exception Codes:       EXC_I386_GPFLT

               

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

              0   libViewSystem.dylib           0x000000010a380ebc IView::NeedsDisplay(bool) + 24

              1   com.filemaker.client.advanced12 0x0000000108ca932b TabLayoutObjectView::PanelsNeedDisplay(bool) + 53

              2   libViewSystem.dylib           0x000000010a357b25 BaseView::RemoveFromParent() + 57

              3   com.filemaker.client.advanced12 0x0000000108c8fd5d LayoutObjectView::OnMessage(unsigned long long, void const*, unsigned long) + 157

              4   libViewSystem.dylib           0x000000010a389960 ViewSystem::DispatchUserMessageToView(IView*, ViewSystem::Message const&) + 76

              5   libViewSystem.dylib           0x000000010a389654 ViewSystem::DispatchRawMessageToView(IView*, ViewSystem::Message const&) + 40

              6   libViewSystem.dylib           0x000000010a389c3f ViewSystem::DispatchImmediateMessages() + 187

              7   libViewSystem.dylib           0x000000010a3b3753 Animation::SetAllowAnimation(bool) + 39

              8   com.filemaker.fmengine.framework 0x000000010b0bb665 Draco::ScriptRuntimeBase::HaltScript() + 199

              9   com.filemaker.fmengine.framework 0x000000010b0bbcba Draco::ScriptRuntimeBase::ExitStackFrame(bool, bool) + 230

              10  com.filemaker.fmengine.framework 0x000000010b0bc5db Draco::ScriptRuntimeBase::DoNextStep() + 379

              11  com.filemaker.fmengine.framework 0x000000010b0bc3f9 Draco::ScriptRuntimeBase::DoRunLoop() + 203

              12  com.filemaker.client.advanced12 0x00000001086ddfb0 ScriptRuntime::OnIdle() + 72

              13  com.filemaker.fmengine.framework 0x000000010b0a9b37 Draco::FMSession::OnIdle(bool) + 69

              14  com.filemaker.client.advanced12 0x000000010858aded CFMProApp::Idle(bool) + 95

              15  com.filemaker.client.advanced12 0x000000010858c05c CFMProApp::DispatchNullEvent() + 180

              16  com.apple.CoreFoundation       0x00007fff95adf45c __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12

              17  com.apple.CoreFoundation       0x00007fff959cf634 _CFXNotificationPost + 3140

              18  com.apple.Foundation           0x00007fff8d04b8c6 postQueueNotifications + 782

              19  com.apple.CoreFoundation       0x00007fff95a3f127 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23

              20  com.apple.CoreFoundation       0x00007fff95a3f080 __CFRunLoopDoObservers + 368

              21  com.apple.CoreFoundation       0x00007fff95a312ba __CFRunLoopRun + 1178

              22  com.apple.CoreFoundation       0x00007fff95a30bd8 CFRunLoopRunSpecific + 296

              23  com.apple.HIToolbox           0x00007fff955dc56f RunCurrentEventLoopInMode + 235

              24  com.apple.HIToolbox           0x00007fff955dc2ea ReceiveNextEventCommon + 431

              25  com.apple.HIToolbox           0x00007fff955dc12b _BlockUntilNextEventMatchingListInModeWithFilter + 71

              26  com.apple.AppKit               0x00007fff8985b8ab _DPSNextEvent + 978

              27  com.apple.AppKit               0x00007fff8985ae58 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 346

              28  com.apple.AppKit               0x00007fff89850af3 -[NSApplication run] + 594

              29  com.filemaker.client.advanced12 0x00000001084bafad CMacApp_Main + 501

              30  com.filemaker.client.advanced12 0x0000000108580370 main + 49

              31  libdyld.dylib                 0x00007fff8dbb35c9 start + 1

              • 4. Re: Print Setup script step transferred from 14 to 15 caused crash
                TSGal

                michaelp:

                 

                Thank you for the crash report.

                 

                The cause seems to be related to a tab control/panel on the layout.  Please describe what objects are on the layout?

                 

                1. Duplicate the layout.

                2. In the duplicated layout, remove any tab panels.

                3. Temporarily modify the script (or duplicate the script) so that it calls the duplicated layout.

                4. Run the script.

                 

                Does this still crash?  If so, please only post the crashed thread.

                 

                TSGal

                FileMaker, Inc.

                • 5. Re: Print Setup script step transferred from 14 to 15 caused crash
                  michaelp@alchemy

                  I did as you instructed and the blank layout didn’t cause a crash.  However, I switched the script back again to the crashing layout and script step order and it is not crashing today.  Since the last time when it was crashing I had closed the solution overnight and slept my computer.  It seems to be working now regardless of the configuration of steps or layout elements.

                   

                   

                  Michael Primrose

                  Alchemy Consulting Group, LLC

                  FileMaker  13 & 14 Certified Developer

                  FileMaker Business Alliance Platinum Member

                  http://www.alchemyg.com <http://www.alchemyg.com/> - 888-663-6382