You can test this in the attached database, form Test.  That also display the corrupted check box problem in 5.3.0.3.

I have other problems with this release as well, including a database that won't load at all under Windows 10 (just crashes out), and one that will load on ubuntu but refuses to show re-populated list boxes when the contents are set by macros (the data is there, it just doesn't display until I type a letter), but I haven't got these into manageable reproducible form as yet (they work on a remote database that I don't want to distribute).  I'm trying.....

Sorry, that should be Form table1, not test.

Possibly related, or the same as this bug:  https://bugs.documentfoundation.org/show_bug.cgi?id=105759

Couldn't confirm this buggy behavior with the attachment.

Tested with LO 5.3.0.3 and OpenSUSE 42.1 64bit Linux rpm.

Strange.  

Let me just restate the actions need to cause this problem on my Ubuntu and Windows systems, in case I wasn't crystal clear.

Open the database.
Open form table1 for edit and edit something (eg the size of a field).
Save form table1.
Close form table1.
Then 'File', 'Exit' and when prompted 'Save'

Hangs.  I have to force close Base.

(In reply to tim from comment #5)
> Strange.  
> 
> Let me just restate the actions need to cause this problem on my Ubuntu and
> Windows systems, in case I wasn't crystal clear.
> 
> Open the database.
> Open form table1 for edit and edit something (eg the size of a field).
> Save form table1.
> Close form table1.
> Then 'File', 'Exit' and when prompted 'Save'
> 
> Hangs.  I have to force close Base.

Have done all this. First I have excluded macros, then for a second test included macros. No difference. I have 
saved the form, 
wanted to close the document, 
have been asked, if I want to save the changed contend
save
closed - without problem.
Note: If I do the same with a table I got a hang - see bug 105759.

Did you try this with a new user-profile?

I just tried with a new user - no change.  It still hangs.

On Ubuntu I on Version: 5.3.0.3
Build ID: 1:5.3.0~rc3-0ubuntu1~yakkety1.1
CPU Threads: 8; OS Version: Linux 4.8; UI Render: default; VCL: x11; Layout Engine: new; 
Locale: en-GB (en_GB.UTF-8); Calc: group

On Windows 10 I downloaded the latest 64 bit from the Libreoffice download website yesterday (7/2/17).

I could reproduce with
Version: 5.4.0.0.alpha0+
Build ID: 653e181fb831a04c2845d99f79f72454a88bb948
CPU Threads: 4; OS Version: Linux 4.1; UI Render: default; VCL: kde4; 
TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2017-02-07_22:17:53
Locale: de-DE (de_DE.UTF-8); Calc: group

Also with 
Version: 5.3.1.0.0+
Build ID: c9ab894ae846185a0341656922b0aa1632bfe886
CPU Threads: 4; OS Version: Linux 4.1; UI Render: default; VCL: kde4; Layout Engine: new; 
TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:libreoffice-5-3, Time: 2017-01-23_00:14:42
Locale: de-DE (de_DE.UTF-8); Calc: group

... and after starting the developement-builds I have the same error with LO 5.3.0.3

Will try to restart LO after logging out and logging in.

I'm glad to see I'm not alone. Thanks for pursuing this.

Tested with

Version: 5.3.0.2
Build ID: 5ad7b2889021c491af62f7930a4b1cb631392f16
CPU Threads: 2; OS Version: Mac OS X 10.12.2; UI Render: default; Layout Engine: new; 
Locale: fr-FR (fr_FR.UTF-8); Calc: group

Reproduced

Created attachment 131033 [details]
Backtrace - looks to be mutex lock

From the backtrace, the problem appears to be linked to a mutex lock

Seems OK in Version: 5.3.1.1
Build ID: 1:5.3.1~rc1-0ubuntu1~yakkety0

Has something been fixed?

I can't help here, I don't even reproduce the pb with master sources updated yesterday => uncc myself

Definitely fixed in the latest release:

Version: 5.3.1.2
Build ID: 1:5.3.1-0ubuntu1~yakkety0
CPU Threads: 8; OS Version: Linux 4.8; UI Render: default; VCL: x11; Layout Engine: new; 
Locale: en-GB (en_GB.UTF-8); Calc: group

Closing as RESOLVED WORKSFORME as per comment 16.
Thanks for testing it.