It seems it's a known chrome bug: https://code.google.com/p/chromium/issues/detail?id=498074
No change or solution in the latest release.
This issue was fixed after chromium was updated to 47.0.2526.73 release.