xwords/xwords4/android/app/src/main
Eric House fb15039b60 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-05-29 15:51:09 -07:00
..
assets up strings for new release 2019-04-25 15:20:21 -07:00
java/org/eehouse/android/xw4 assert refcount never climbs after reaching 0 2019-05-29 15:51:09 -07:00
res remove exif data from image files 2019-05-20 06:41:47 -07:00
AndroidManifest.xml get rid of DispatchNotify 2019-04-04 12:52:28 -07:00