Thank you for reporting this. I have done a lot of work in the registration engine to prevent this from happening in the future.
Basically, the amount of starpairs between the frames put limits on memory and cpu usage at the same time when the total amount of star pairs become bigger then a couple of 1000 star pairs.
Reason being, to calculate a homography between 1000 stars, APP needs
(1000*2 (x,y coordinate) * 8 (double precision calculation) )^2 bytes
for the Hessian Matrix in the regression.
For 1000 stars this means = 256MB of memory. This is no problem
2500 stars between two frames => 1.6GB now it starts to become a problem.
To solve this problem for different maximum amounts of memory available to APP, I have built in dynamically scaling of the registration engine for both the amount of memory that is needed and the number of CPUs that are/can be used. The scaling is done such that the memory usage can’t top the available amount of memory to APP and thereby preventing future Out of Memory errors.
Also the amount of stars that can be used in the registration is now capped depending on the available MAX memory for APP.
From version 1.038, this “out of memory” bug in the registration engine should be a thing of the past I hope ;-)