Hey guys! The op for the MCPatcher thread found out why you may get Out of Memory and white block issues with his patcher. Here is a good way of looking at it.
Minecraft gets allocated in 3 parts.
1) Interpreter (Java itself)
2) Java Heap (Memory for Minecraft)
3) Texture Memory (All the stuff we see)
On 32-bit Java this is capped at 2GB due to an OS limit. So if you set the Java heap too high then that leaves less for textures and the interpreter itself. In that event you can get out of memory and white box problems. Lowering your heap cap works to resolve the issue. In other words if you are getting Out of Memory errors or white box issues then reduce the -Xmx setting and drop the -Xms one. That op on that thread got it working fine with -Xmx768m and that was with HD textures and on 32-bit Java.
I had done alot of research when someone over there mentioned that the sole act of changing from 32-bit to 64-bit Java resolved the issue for them. The reason why 64-bit version takes care of it is because that 2GB application limit disappears and the actual limit is far higher than we have installed ram in 99% of cases right now. 8TB (yes Terabytes) to be exact.
MSDN Technical article concerning memory limits in Windows:
http://msdn.microsof...8(v=vs.85).aspx
Proof that less is more here.
Tested: 32-bit Java, HD Patched, x256 LB Photo Realism texture pack
Commandline: "%programfiles(x86)%\Java\jre6\bin\java.exe" -Xincgc -verbose:gc -Xmx768m -jar MineCraft.exe
Picture shows running with 768MB heap allocation. 96% allocated and 53% in use.
Note that the command was structured to force 32-bit Java use on 64-bit OS but the same 2GB barrier applies which makes the test valid.
Image: