Comment 4 for bug 1580195

I bisected this and it turned out to be much older than I expected. Looks like it happened between 2015-09 and 2015-11, though beyond that I'm not sure. We don't have any rc-proposed images old enough for a more fine-grained inspection.

Problem exists in:
* krillin rc-proposed 329 (pay-service 15.10+15.04.20160413-0ubuntu1)
* krillin rc-proposed 315 (pay-service 15.10+15.04.20160324.1-0ubuntu1).
* arale rc-proposed 306 (pay-service 15.10+15.04.20160324.1-0ubuntu1).
* arale rc-proposed 262 (pay-service 15.10+15.04.20160114-0ubuntu1) (oldest rc-prop image on our servers).
* krillin rc 39 (OTA 8.5) (pay-service 2.0.0+15.04.20151103-0ubuntu1)
* krillin stable 27 (OTA 8) (pay-service 2.0.0+15.04.20151103-0ubuntu1)

I don't see the issue in:
* krillin stable 26 (OTA 7) (pay-service 2.0.0+15.04.20150914-0ubuntu1)
* krillin stable 24 (OTA 5) (pay-service 2.0.0+15.04.20150706-0ubuntu1)

BTW, this is really easy to check for. Flash an image, go to the app store, tap a paid app (I've been using "Cut the Rope" since it's on the front page today), tap the $2.99 button. Watch 'top' in a shell at the same time, to see if pay-service jumps up to 99% CPU. No need to even try to log in; it's sufficient to merely bring up the login UI.