Program crashes when portals have container fields with referenced files

Issue report by Shakib

Product

FileMaker Pro

Version

13.0v5 Middle East and India

Operating system version

Mac OSX 10.10.3

Description of the issue

Filemaker pro quits unexpectedly after closing (or while opening) a database that has 3 related tables with a layout that has a portal and container fields.

Steps to reproduce the problem

1. Create a database with 3 tables: Events, Files, Alternative versions. The Files and Alternative Versions are related to Events in a way that Events is the "one" side of relationships and Files and Alternative Versions are "Many" sides of relationships. Please see the photo.
2. Within Files and Alternative Version tables, create 2 Container fields.
3. Create a layout based on the Events table. Add 2 portals to this layout in a way that each portal is based on either Files or Alternative Version tables. Include all the container fields in these portals.
4. Create a few records in each table and relate the records to each other (i.e. a few records in Files table to Events table, etc.)
5. In the container fields of each record of the Files and Alternative Versions tables, insert a file using "Store only a reference to the file" option.
6. Repeat adding a few records and files within container fields using the above-mentioned layout.
7. Close the file.

(Please note that I am using a Middle eastern version but none of the field names, file names, etc. are in Arabic letters. Just Arabic text within fields in some records. )

Expected result

Database file should be opened and closed without any issue in multiple attempts of closing and opening.

Actual result

The program crashes right after closing the database or right before opening it again. The crash happens about 60% to 90% of the times that an opening or closing attempt is made. I have checked this issue on 3 computers: one macbook pro, one iMac, one Windows (although in Windows, it crashed only 2 times out of 6 tries)

Exact text of any error message(s) that appear

[I have copied the following from the Recovery file created after the crashes]

Timestamp Filename Error Message
2015-06-11 19:37:13.435 -0400 Test from scratch-for testing portals.fmp12 0 *** Started consistency check of improperly closed file, total of 81 block(s) to check
2015-06-11 19:37:13.435 -0400 Test from scratch-for testing portals.fmp12 0 Reset maximum block sequence number to 4920
2015-06-11 19:37:13.436 -0400 Test from scratch-for testing portals.fmp12 0 *** Completed consistency check, checked 81 block(s)
2015-06-11 19:38:40.272 -0400 Test from scratch-for testing portals.fmp12 0 *** Started consistency check of improperly closed file, total of 81 block(s) to check
2015-06-11 19:38:40.273 -0400 Test from scratch-for testing portals.fmp12 0 Reset maximum block sequence number to 4920
2015-06-11 19:38:40.273 -0400 Test from scratch-for testing portals.fmp12 0 *** Completed consistency check, checked 81 block(s)
2015-06-11 20:04:49.606 -0400 Test from scratch-for testing portals.fmp12 0 *** Started consistency check of improperly closed file, total of 81 block(s) to check
2015-06-11 20:04:49.610 -0400 Test from scratch-for testing portals.fmp12 0 Reset maximum block sequence number to 4920
2015-06-11 20:04:49.611 -0400 Test from scratch-for testing portals.fmp12 0 *** Completed consistency check, checked 81 block(s)
2015-06-11 20:13:10.705 -0400 For testing portals-1.fmp12 0 *** Started consistency check of improperly closed file, total of 81 block(s) to check
2015-06-11 20:13:10.706 -0400 For testing portals-1.fmp12 0 Reset maximum block sequence number to 5260
2015-06-11 20:13:10.706 -0400 For testing portals-1.fmp12 0 *** Completed consistency check, checked 81 block(s)

Screenshot