Ugly workaround for some unexpected and undocumented behavior in one of the Windows graphics library calls. SetDIBitsToDevice has some finicky requirements about what sort of memory it can consume. The requirements aren't documented, so this fix applies a folk remedy I found on the Internet. I've put in a TODO for me to find out exactly what is *really* going on with this function, but I'm  checking in the quick fix since I don't have time now to drill down on  this in more detail.
Ugly workaround for some unexpected and undocumented behavior
in one of the Windows graphics library calls. SetDIBitsToDevice has
some finicky requirements about what sort of memory it can consume.
The requirements aren't documented, so this fix applies a folk
remedy I found on the Internet. I've put in a TODO for me to find
out exactly what is *really* going on with this function, but I'm 
checking in the quick fix since I don't have time now to drill down on 
this in more detail.

Review URL: http://codereview.chromium.org/549089

git-svn-id: 721b910a23eff8a86f00c8fd261a7587cddf18f8@1375 fcba33aa-ac0c-11dd-b9e7-8d5594d729c2

sbc100/native_client,sbc100/native_client,nacl-webkit/native_client,nacl-webkit/native_client,sbc100/native_client,nacl-webkit/native_client,sbc100/native_client,nacl-webkit/native_client,sbc100/native_client,sbc100/native_client,nacl-webkit/native_client