In the FAQ, titled the same, it says virtural memory is not use by reality capture and to report it as a bug is if it does.
https://support.capturingreality.com/hc/en-us/articles/115001483771-Huge-scene-reconstruction
Reality capture is most definitely using a lot of virtual memory. 38.8GB commit with 14.2GB working set, It shows RC accessing pagefile, and 6540 page faults/sec.
Hello Steven,
what version and license of RC do you use? How many images are you processing and what alignment settings did you use?
In that example it is only 900 or so photos, but I have now add more and am now at the 2500 limit. I’m using the steam paid version. This behavior seems to be normal, as it has been working like this for years. It was my understanding that alignment would use as much RAM as needed to for the amount of features you have selected in you settings, and that other processing after would be out of core (like depth mapping). At the time I was told this by Wishgranter. I assumed he worked for Capturing Reality, as he was very knowledgeable and responded to almost every post, but have been told by the forum that he was just a guy helping out.
This maybe the real bug. These last few parts are taking way longer and a lot more memory to compute. It’s weird that the 5Mil vertices parts maxed out at 11GB of ram and these 24-50 vertices parts are using 50-70GB of ram or so.
If I cancel now wont it have to start over at part one? I’m worried starting over from part 1 would be slower than just letting it finish at this rate
I don’t think the log file would be helpful here, but if there is some files I could provide to help track down bug to be fixed in future revisions I would be happy to provide.
Hello Steven,
regarding the memory consumption during the alignment, I can see from your first screenshot that you used very high values for the detected features which consumes too much RAM. In this case please try to lower the number of detected features and try again.
Regarding the memory consumption during the reconstruction, it looks like bug on our side, we will take a look at it. In the meantime can you please try the workaround proposed in the article you have mentioned in your original post https://support.capturingreality.com/hc/en-us/articles/115001483771-Huge-scene-reconstruction ?
If you abort the reconstruction, then only depth-maps are reused but the model parts are calculated again.
I followed the steps from the FAQ and then just gave up and let the model finish over the week end, but now cant validate steam license and cant save the work 
I’m heart broken.
Hello Steven,
I hope that we have managed to solve your licensing problems via email and that you are able to use RC now.
Have you tried using the workflow proposed in the article I have posted in my prvious message?
The licensing problem has been solved. Thank you for reaching out.
The only method I wasn’t able to try was the last one splitting up the workload. I just let my machine work through the problem and it turned out ok.
Please, don’t hesitate to ask for a log, crash dump, ect… I’ll link the whole project if it would help track down the bug.