You can probably replace any malloc except the one on line 20 of functions.cpp, but they should all be pretty small anyway. I'm guessing it's the seam map that's growing too large, but if you set --cache-threshold=1 that should cache all the images before it gets to the seam map and might give you enough RAM to finish.
I'll try to implement cacheable, reallocable Flex class data in a future version. On Saturday, 3 April 2021 at 17:14:29 UTC+1 [email protected] wrote: > Question: Any possibility to convert some of the mallocs to MapAlloc? > Could this prevent some OOM cases I encountered when blending very large > scans (1.2g+0.8g 8-bit tiffs)? -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/377336d4-3e1b-4cda-af6f-6076f5cde8b2n%40googlegroups.com.
