[dogma1138]

WDDM 2.0 gpummu is supposed to ensure that the memory has been zeroed between different applications that use virtual GPU memory.

If this is the case there might be a compliance issue on nVidia side which makes me wonder if webgl is vulnerable also.

WebGL was amended to request a zero when provisioning or disposing of a buffer but it relies on the API which is handled by the driver if nVidia is taking some shortcuts to save time it might be possible to leech stale memory this way.

[exDM69]

> WDDM 2.0 gpummu is supposed to ensure that the memory has been zeroed between different applications that use virtual GPU memory.

Which Windows version introduced this WDDM version? Could it be that OP is running an older version?

> WebGL was amended to request a zero when provisioning or disposing of a buffer but it relies on the API

This is indeed a tricky situation. All modern GPUs do "zero bandwidth clears" which means that upon clearing, nothing gets written to the actual framebuffer, the memory is just marked "cleared" (by writing some special bits to the L2 cache, for example). This makes it difficult to reason whether there's any sensitive content left in the framebuffer.

edit: nevermind, the OP seems to be using OSX, so it's not WDDM. Additionally, the OSX GPU drivers are written by Apple.

[dogma1138]

Yeah this was confusing he said that it was an Nvidia issue which is why I thought it was on Windows.

As far as WDDM goes 2.0 requires that for sure I'm pretty sure this was part of the original WDDM GPUMMU spec also but I can't really find those details anymore on MSDN since most of the pages refer to 2.0 atm.