AnsweredAssumed Answered

Closing Window with Iteractive Container Field Causes Crash (Full Repro Steps Included)

Question asked by disabled_excrubulent on Jun 30, 2013
Latest reply on Jul 4, 2013 by disabled_excrubulent

Summary

Closing Window with Iteractive Container Field Causes Crash (Full Repro Steps Included)

Product

FileMaker Pro

Version

FMPA 12.0v4 & 12.0v3 (at least - I haven't tested on other versions)

Operating system version

Windows 7 64-bit

Description of the issue

Opening a Filemaker layout window with a container field in it, set to show interactive content, then closing it at least twice causes filemaker to crash to desktop.

Steps to reproduce the problem

1 Create a new file in FMPA 12

2 add a single container field to the existing table

3 create a layout with an edit box displaying this container field and optimised to show interactive content

4 create an empty layout and view in Browse mode

5 open the manage layouts dialog, select the container layout and press 'open'

6 close the newly open layout window

7 repeat 5 & 6 one more time

8 crash to desktop


Alternatively:

Perform steps 1, 2 & 3

4 view the layout with the container field in browse mode, and close the database by clicking on the X button on the layout window

5 reopen the database without closing filemaker

6 Repeat step 4

7 crash to desktop



So it appears that closing the layout that has a container field set to show interactive content at least twice - whether the database gets closed or not - crashes Filemaker.

Sometimes filemaker will crash after closing the window only once, but that doesn't seem to be as common.

Changing the edit box's properties to be optimised for images rather than interactive content causes the problem to go away.

Expected result

The window should close without crashing Filemaker.

Actual result

Filemaker crashes.

Exact text of any error message(s) that appear

Two error messages appear each time.  Both messages start with this text (you're probably familiar with Windows' crash message):

"Filemaker Pro Advanced has stopped working.

Windows can check online for a solution to this problem.

Button:  Check online for a solution and close the program

Button:  Close the program

Button:  View problem details"

Dismissing the window in any way for the first message causes the second message to appear.

Clicking on "View problem details" for each message reveals these two Problem signatures:

Message 1:

Problem signature:
  Problem Event Name:     APPCRASH
  Application Name:     FileMaker Pro Advanced.exe
  Application Version:     12.0.4.403
  Application Timestamp:     514b6292
  Fault Module Name:     ntdll.dll
  Fault Module Version:     6.1.7601.17725
  Fault Module Timestamp:     4ec49b8f
  Exception Code:     c015000f
  Exception Offset:     00084621
  OS Version:     6.1.7601.2.1.0.256.48
  Locale ID:     3081
  Additional Information 1:     0a9e
  Additional Information 2:     0a9e372d3b4ad19135b953a78882e789
  Additional Information 3:     0a9e
  Additional Information 4:     0a9e372d3b4ad19135b953a78882e789

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt


Message 2:

Problem signature:
  Problem Event Name:     APPCRASH
  Application Name:     FileMaker Pro Advanced.exe
  Application Version:     12.0.4.403
  Application Timestamp:     514b6292
  Fault Module Name:     ntdll.dll
  Fault Module Version:     6.1.7601.17725
  Fault Module Timestamp:     4ec49b8f
  Exception Code:     c0150010
  Exception Offset:     000847db
  OS Version:     6.1.7601.2.1.0.256.48
  Locale ID:     3081
  Additional Information 1:     60e0
  Additional Information 2:     60e0e94b220fa8ded52b12abf8c6325e
  Additional Information 3:     2d9c
  Additional Information 4:     2d9cc474d11efc1bb22ad56a20348b64

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

Workaround

Switching to another layout (eg, an empty layout) before closing the window prevents the crash.  Going to File > File Options -> Script Triggers -> On Window Close and setting a script to switch to an empty layout prevents the crash.

Outcomes