Jul-17-2017, 09:26 PM
Works for me, the last lines are:
Output: 195: 8437.0 / 32010.0 MiB used (26.36%); 5850000 objects
196: 8451.0 / 32010.0 MiB used (26.40%); 5880000 objects
197: 8465.0 / 32010.0 MiB used (26.44%); 5910000 objects
198: 8480.0 / 32010.0 MiB used (26.49%); 5940000 objects
199: 8494.0 / 32010.0 MiB used (26.54%); 5970000 objects
Done: 8508.0 / 32010.0 MiB used (26.58%); 6000000 objects
================================ Sphere created ================================
Position ( 0.00000, 0.00000, 0.00000) [m]
Radius 1.00000 [m]
Mass 100.00000 [kg]
Total mass of elements 100.00000 [kg]
density 27.28370 [kg/m^3]
Operating systems work like airlines, they overbook (over-allocate) memory because many processes don't really use all the memory they ask for. But when a process insists in getting the promised memory, while the OS cannot fulfill the promise, the process is summarily killed (because it"s too late to give it a return code). Airlines aren't there yet :)
Unless noted otherwise, code in my posts should be understood as "coding suggestions", and its use may require more neurones than the two necessary for Ctrl-C/Ctrl-V.
Your one-stop place for all your GIMP needs: gimp-forum.net
Your one-stop place for all your GIMP needs: gimp-forum.net