For reference the 64-bit LDView 4.2 Beta 1 settled at 506MB of memory after loading the file when memory usage was set to Low (with standard settings, non-low-quality studs, and edges plus conditional edges). With memory usage set to High, it settled at 2,282MB (2.22GB), which may or may not work on a 32-bit build, which maxes out between 2-3.5GB depending on system settings. However, while the file was loading, I noticed usage over 5GB, which would have definitely crashed the 32-bit build. As a matter of fact, it locked up everything on my system except the mouse for a minute or two, but surprisingly, everything came back, and LDView even worked (albeit slowly).
In addition to setting memory usage to low, I would strongly suggest checking the "Low quality studs" option, and disabling edge lines. (The edge lines completely wash out the image, anyway.) Doing this, memory usage was 447MB (not all that much lower than with high-quality studs and edge lines).
In addition to setting memory usage to low, I would strongly suggest checking the "Low quality studs" option, and disabling edge lines. (The edge lines completely wash out the image, anyway.) Doing this, memory usage was 447MB (not all that much lower than with high-quality studs and edge lines).