I can confirm this problem for the sid package 50.0.2661.75-1 when installed on testing. However, the problem does not occur with the package 50.0.2661.75-1~deb8u1 from stable-security on testing, although it's basically the same version of chrome. Cheers, Marc