Device name: Pixel XL and a friend's Nexus 6P

From "Settings > About Chrome" 
Application version: Dev 59.0.3056.4 / 	
Chrome Dev 59.0.3050.4 and maybe a version before, too.
Operating system: 7.1.2 Beta (NPG47I) (7.1.1 on friend's 6p)

URLs (if applicable): none

Steps to reproduce:
(1) Install Chrome Dev
(2) Get/Install a Play Services Update
(3) Have bad luck

Expected result:
Normal battery usage

Actual result:
Severe battery drain through wakelocks (SyncLoopWakeLock)

So I noticed severe battery drain with Google Services using over 20% up to 30% of battery and was wondering what was up with that. So I installed a battery watching app and it pointed to SyncLoopWakeLock. Then I checked my Account > Google settings and saw that Chrome Dev was constantly trying to sync (Syncing...) but apparently failing and therefore causing the wakelocks. Trying to remember what I did before, I installed a Google Play Services app manually (from an APK) led me to believe it was actually a GPS update that caused it. So I downgraded the version and reset my sync status. Later I was auto updated to a newer GPS and the issue started happening again, again Chrome Dev sync got stuck and I had to untoggle and retoggle the sync option to fix it. 

I figured I just broke something by manually updating GPS and it was a one time thing but two days ago a friend told me that he had severe battery drain on his 6p and just for the heck of it, I asked him to install the same battery monitoring app and look for wakelocks. Lo and behold, it is the same SyncLoopWakeLock and Chrome dev failing to sync for him, too.

Sadly I don't have any logs but I hope this already helps you guys finding a bug.

 

Deleted: 17 - 1.webp 73.6 KB

	17 - 1.webp 73.6 KB View Download