Eric House ce26696a37 assert refcount never climbs after reaching 0 ... Looking for a common but not-yet-reproducible situation where the gamelock gets stuck preventing a game from being opened, usually related to a move arriving. One thing that looked wrong is it seemed possible to have the refcount drop to 0 then get increased again, causing somebody to thing he has a lock when it's actually unlocked. So assert to try to catch that case (and synchronize to make it much harder.)		2019-06-23 10:20:16 -07:00
..
src	assert refcount never climbs after reaching 0	2019-06-23 10:20:16 -07:00
build.gradle	up strings for new release	2019-06-23 10:20:16 -07:00
debug.keystore	include debug keystore directly	2017-01-22 15:35:02 -08:00
proguard-rules.pro	tweak comments	2017-07-19 06:16:22 -07:00