[ptx] hugin has problems with particular imageset
Rich
rich at hq.vsaa.lv
Fri Jun 17 15:35:27 BST 2005
it seems that kuickshow from kde 3.4.1 sometimes recognizes that
something is wrong with that image - it simply refuses to open it,
instead of crashing or looping. though next time when i try to open it,
kuickshow kuickly eats 1gig of ram and then stays there.
maybe somebody has an idea what is going on and why ?
i can reproduce this problem with particular imageset every time, so
even if this is some sort of race condition, it is not very specific.
Rich wrote:
> i have 18 images in a project.
> if i try to stich them (choosing multiple tiff as an output), hugin
> takes ~2gb of ram for each image, processes 16 images (and stops without
> visible reason) - and these images seem to be damaged.
>
> i tried opening them with kuickshow, gimp, identify (from imagemagick) -
> these tools crashed (kuickshow), grew a lot of temporary data (gimp) or
> simply went into loop for a long time so that i had to kill them
> (identify & kuickshow).
>
> i've put an example image here :
> http://evf.lv/stuff/out0000.tif
> (it's 19mb)
>
> what is wrong with this image ? should i report this to
> gimp/kuickshow/imagemagick developers ?
>
> if anybody is willing to look into this i could put up for download
> whole project, so that somebody could try to reproduce this - or i could
> run hugin with strace or do any other debugging.
>
> when i tried to remove most images, leaving two of them, they were
> processed normally.
>
> using hugin cvs-050602
--
Rich
More information about the ptx
mailing list