It would appear that when executing a Shader, Flash starts with an uninitialized register state. Therefore, if a Shader program fails to load a texture or constant or other value into the output register, it is possible to leak memory content.
The attached SWF demonstrates this; it may be neccessary to reload the SWF multiple times before you get lucky and leak some non-zero memory content. An image is attached as an example of what it can look like when the leak triggers (Linux x64).
This bug is subject to a 90 day disclosure deadline. If 90 days elapse
without a broadly available patch, then the bug report will automatically
become visible to the public.
