Features computation out of memory error when processing lots of images
Currently FeatureComputerManager keeps all the created objects across all registered images in memory before committing them to the database. We need to adopt a system to commit objects to the database after each image while still enabling a roll back mechanism if any error occurs before all images have been processed.