AnsweredAssumed Answered

FIleMaker 11/12 Crash when closing window

Question asked by JohnDuncan on Aug 19, 2012
Latest reply on Dec 5, 2017 by TSGal

Summary

FIleMaker 11/12 Crash when closing window

Product

FileMaker Pro

Version

11.0, 12.0

Operating system version

MacOS-X 10.7.4, Windows XP, Windows 7

Description of the issue

This has been an ongoing problem with a complex database.  Occasionally it would crash, usually after about the 3rd print operation.  I was finally able to track it down and verified that it occurs on both platforms and with FileMaker 11 or 12.

The problem occurs after the 3rd sequence of events of:

From Database "A" call a script in Database "B" (which is hidden) which: opens a new window, changes layouts, does a search, changes layouts again, enter prevue mode pause, save as PDF (or print) and then do the following script steps with the preview window showing:

Go To Layout (a different layout on a different table with no records)
Enter Browse Mode
Adjust Window [Resize to Fit]
Set Window Title[Current Window; Get( FileName )]
Close Window [ Current Window ]

The problem doesn't always occur but I have found if I reboot my system and do it 3 times it will always fail.

Steps to reproduce the problem

This problem is very difficult to reproduce outside of the full solution.  I have tried to create a separate database that simulates the steps that it takes to reproduce the problem but it does not fail in the simple database.

Expected result

FileMaker should not crash

Actual result

FileMaker crashes on the "Close Window" step on the 3rd pass through.

Exact text of any error message(s) that appear

No specific error message other than FileMaker crashes.  Here is the first part of the CrashLog from FM Pro Advanced 12.0v2 on MacOS-X 10.7.4

---------------------------------

Process:         FileMaker Pro [452]
Path:            /Volumes/VOLUME/*/FileMaker Pro Advanced.app/Contents/MacOS/FileMaker Pro
Identifier:      com.filemaker.client.advanced12
Version:         12.0.2 (12.0.2)
Code Type:       X86 (Native)
Parent Process:  launchd [277]

Date/Time:       2012-08-17 22:18:04.678 -0400
OS Version:      Mac OS X 10.7.4 (11E53)
Report Version:  9

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

Exception Type:  EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000

Application Specific Information:
objc[452]: garbage collection is OFF
[452] stack overflow

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib             0x92c2d9c6 __pthread_kill + 10
1   libsystem_c.dylib                  0x9b518f78 pthread_kill + 106
2   libsystem_c.dylib                  0x9b509ce3 __abort + 198
3   libsystem_c.dylib                  0x9b50664a __stack_chk_fail + 253
4   com.filemaker.fmengine.framework     0x04178bc3 Draco::FMWindowModel::~FMWindowModel() + 979
5   com.filemaker.client.advanced12     0x0021b6a0 FMDocWindow::~FMDocWindow() + 528
6   com.filemaker.client.advanced12     0x0017b2dc FMAppSession::DeleteWindow(Draco::FMWindowModel&) + 60
7   com.filemaker.fmengine.framework     0x0416fbb0 Draco::FMSession::CloseWindow(Draco::FMWindowModel&, bool) + 352
8   com.filemaker.fmengine.framework     0x041724db Draco::FMWindowModel::CloseWindow() + 43
9   com.filemaker.fmengine.framework     0x0418607a Draco::ScriptRuntimeBase::DoCloseWindow() + 186
10  com.filemaker.fmengine.framework     0x04193f13 Draco::ScriptRuntimeBase::DispatchStep() + 5795
11  com.filemaker.fmengine.framework     0x041946c5 Draco::ScriptRuntimeBase::Execute() + 597
12  com.filemaker.fmengine.framework     0x04195133 Draco::ScriptRuntimeBase::DoNextStep() + 371
13  com.filemaker.fmengine.framework     0x0419525d Draco::ScriptRuntimeBase::DoRunLoop() + 109
14  com.filemaker.client.advanced12     0x0032215f ScriptRuntime::OnIdle() + 127
15  com.filemaker.fmengine.framework     0x0416f010 Draco::FMSession::OnIdle(bool) + 272
16  com.filemaker.client.advanced12     0x0017b802 FMAppSession::OnIdle(bool) + 66
17  com.filemaker.client.advanced12     0x0016abf5 CFMProApp::Idle(bool) + 69
18  com.filemaker.client.advanced12     0x0016ad1d CFMProApp::DispatchNullEvent() + 109
19  com.filemaker.client.advanced12     0x004b37a9 -[MFAppDelegate HandleIdleNotification] + 25
20  com.apple.Foundation               0x94eb4df1 __-[NSNotificationCenter addObserver:selector:name:object:]_block_invoke_1 + 49
21  com.apple.CoreFoundation           0x95348903 ___CFXNotificationPost_block_invoke_1 + 275
22  com.apple.CoreFoundation           0x95313688 _CFXNotificationPost + 2776
23  com.apple.Foundation               0x94eb4db7 -[NSNotificationCenter postNotification:] + 115
24  com.apple.Foundation               0x94f1c803 postQueueNotifications + 948
25  com.apple.CoreFoundation           0x9532c0ce __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 30
26  com.apple.CoreFoundation           0x9532c00d __CFRunLoopDoObservers + 413
27  com.apple.CoreFoundation           0x952fea5d __CFRunLoopRun + 1261
28  com.apple.CoreFoundation           0x952fe1dc CFRunLoopRunSpecific + 332
29  com.apple.CoreFoundation           0x952fe088 CFRunLoopRunInMode + 120
30  com.apple.HIToolbox                0x9c15e723 RunCurrentEventLoopInMode + 318
31  com.apple.HIToolbox                0x9c165a8b ReceiveNextEventCommon + 381
32  com.apple.HIToolbox                0x9c1658fa BlockUntilNextEventMatchingListInMode + 88
33  com.apple.AppKit                   0x993380d8 _DPSNextEvent + 678
34  com.apple.AppKit                   0x99337942 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 113
35  com.apple.AppKit                   0x99333cb1 -[NSApplication run] + 911
36  com.filemaker.client.advanced12     0x0006e7c0 CMacApp_Main + 576
37  com.filemaker.client.advanced12     0x001700e3 main + 67
38  com.filemaker.client.advanced12     0x00050ce1 start + 53

Configuration information

The databases are hosted on FIleMaker Server (MacOS-X 10.6 or 10.7).  The crash occurs on both Windows and Mac platforms.

Workaround

I rewrote the script containing the Close Window to just close the window (without changing layouts, entering browse mode or renaming the window) if there is more than 1 window open in the Database file which seems to have eliminated the problem.

Outcomes