Thank you @keesscherer for this bug and usefull screenshot.
The screenshot shows that you have very high star counts (3000-4000). So I tried to register some frames with that high star counts and only 2GB of memory reserved to APP. I do get the same memory problem, so clearly there is a memory leak in the registration engine.The good news is, that I have located it now, so I’ll fix it.
I am wondering about the high star count, was registration not good with a maximum of 2500 stars, so you decided to increased the limit? (For regular stacks, 1000 stars should normally be enough to get very good registration ) Or just testing?
Regarding speed, I know I can do more optimizations in the integration module regarding outlier rejection of light frames.. I’ll work on that soon, because that’s a clear bottleneck currently…