On 11.07.2015 22:57, Miguel C wrote: > I am at least :| You're not alone. All my FreeBSD 10.1p14/amd64 boxes are affected and this bug forced me to move from chromium to firefox until it's fixed.