hugin-devs team mailing list archive

[rew <678634@xxxxxxxxxxxxxxxxxx>]

This no longer happens with 2010.4. During the "finetune" of just over
1000 points, virtual memory  usaage dropped by 0-60Mb (it went up and
down between these two numbers). Real memory went up and down as well.
It topped out at 1Mb more than before the finetune (on a total of
700Mb).

When the finetune was finished 30Mb more was being used than before.
This did not drop back.

Fix released: it no longer happens.


** Changed in: hugin
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/678634

Title:
  "Fine-tune all points" uses vast amounts of RAM.

Status in Hugin - Panorama Tools GUI:
  Fix Released

Bug description:
  Hi.

I have been using hugin for quite a while now. Recently I made my biggest project yet, with 239 source images (each 6 megapixel) and 6000 control points (generated by autopano-sift).

Running "Fine-tune all points" caused hugin to consume vast amounts of RAM on my computer. In fact, I had to add an extra 4GB of swap just to stop it being killed by the OOM killer. Hugin's virtual size grew to 4.6GB. Luckily I have a 64-bit (Linux) machine, so it was able to cope with that. Once the fine-tuning finished, the memory was freed again.

I think it is likely that some of that RAM could be freed earlier than the end of the task. I would have expected hugin to load image data in on a cache-basis and throw away unused images, like it does normally. If I do the calculations, all those images adds up to 4113MB, so that is probably where all the RAM is going.

Maybe it's as simple as hugin forgetting to free images from its cache between fine-tuning points.

Matthew