Halcon and memory allocation
Halcon, at least when writing data, works only with its own memory area. Namely, its cache.
In view of that, when an operator is fed with a preallocated image whose buffer was allocated outside Halcon, it forgets the preallocated buffer and allocates its own output. Storing it within Halcon's cache.
As a result, the output image's data are located in a different memory location after the operator has been applied.
To avoid multiple allocation for a output objects, use only data allocated through Halcon. Avoid to preallocate output data other ways than Halcon's ones. As it turns in higher resource consumption due to multiple allocations.
Related Articles
Halcon 11 installation on Windows 11
Aggiornare sentinel driver a 9.15. Dopo l'installazione del driver è necessario anche disabilitare l'integrità di memoria in windows 11 (cerchi la voce isolamento core e disabiliti integrità della memoria, riavvii, schermata blu, riavvii e poi ...
Known Alvium's issues
Ticket iMAGE S Ticket AVT Problem Description Camera Model FW Version Status on the field iMAGE S comment Feedback AVT 1009 117202 Incomplete frames, even when a single frame is triggered Manta, and Alviums USB (2050m and 500m) - Probably directly ...