hugin-devs team mailing list archive

[tduell <1529272@xxxxxxxxxxxxxxxxxx>]

Hello fububtu,

On Sun, 27 Dec 2015 02:11:10 +1100, fubuntu <fbugs@xxxxxxx> wrote:

> Thank you for your answer, now this becomes clearer to me. And I realize
> that there was an important information missing in my bug report: The
> GUI actually never shows up, the process gets killed before that. So
> yes, the queue seems to be corrupted, and each time the process gets
> killed it gets worse. Now, how can I clear the queue without the GUI, I
> couldn't find an appropriate command line option for that nor could I
> find the place where this information is stored.
>

I haven't used PTBatcher for a while now, but I have a file in my home dir  
named 'ptbt0' which looks like it may be the batcher queue.
If you have a similar file, try renaming it 'ptbt0.old' or similar and see  
if this helps.

Cheers,
-- 
Regards,
Terry Duell

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

Title:
  Stitching using PTBatcherGUI eats all memory, Hugin_stitch_project
  works

Status in Hugin:
  Incomplete

Bug description:
  
  Stitching a simple pano with a couple of images uses up all memory on my system (8 GB RAM + 8 GB swap) before the operating system kills the process. This can take up to an hour, and the process eating all memory is PTBatcherGUI.

  Switching to Hugin_stitch_project as processor for the same pano
  finishes the stitching within a couple of seconds, using not much
  memory, as expected. This also happens for other photos.

  I am on debian testing with hugin 2015.0.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/1529272/+subscriptions