I don't think this is enough. I think this just mitigates the ability to use high precision to determine cache misses on array accesses. The leaked data is stil

I don't think this is enough. I think this just mitigates the ability to use high precision to determine cache misses on array accesses. The leaked data is still there and the paper says it's one of 64 possibilities. Enabling site isolation helps since it's only process memory. Someone correct me if I misunderstand. EDIT: Also, just confirmed via https://jsfiddle.net/5n6poqjd/ https://jsfiddle.net/5n6poqjd/ that only FF has SharedArrayBuffer disabled. Chrome isn't going to release 64 which has SharedArrayBuffer disabled for a couple of weeks.