Uh, anyone else think this title is a bit sensationalist? I was expecting something a bit more along the lines of actually leaking usable private data, not just displaying a rastered frame.<p>Even further this has very little to do with chrome. The only way chrome could actually fix this issue would be if it nuked the frame buffer when it released it. This is a fine idea, but if I was a dev in that context I would assume the OS would make stronger guarantees than that??<p>If anything, this is an edge case Chrome devs (and other developers) could protect themselves against if they were so inclined, but I&#x27;m not surprised they didn&#x27;t assume they needed to protect against this.