[bradhe]

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.

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??

If anything, this is an edge case Chrome devs (and other developers) could protect themselves against if they were so inclined, but I'm not surprised they didn't assume they needed to protect against this.

[djur]

The primary use case for Incognito Mode, as far as I know, is so a user can casually use a browser without leaving inadvertent artifacts of their usage on the machine. Having a page you visited in Incognito Mode be visible in Chrome after Incognito Mode is closed seems to be precisely the kind of thing users expect the feature to prevent.

[cookiecaper]

If you associate the Chrome browser with your Google account (not just logging in to a Google site, but going to settings and putting the information in there), the history will be synced across several devices. Incognito can be used to prevent pages viewed on your phone or laptop from going to your desktop's history or vice-versa.