hugin-devs team mailing list archive

[Yuv <825756@xxxxxxxxxxxxxxxxxx>]

On August 13, 2011 08:21:12 pm Andrew Happ wrote:
> … it seems to me that enblend may be unable to open the output file
> because a thread process running on the other core is holding the file
> open.  I have never coded in a multi thread environment, so I ask the
> question; is the thread handling automated in the compiler or is the
> programmer crafting the thread timing/synchrony?

Usually this kind of error shows up because of low/insufficient disk
space.

In this case it is triggered by a threading issue.  One possible explanation 
is that the threads running concurrently use more disk space than when they 
are run sequentially.  In a usual situation this would not matter, but in a 
low disk space situation synchronizing the threads might help squeeze disk 
usage through the bottleneck.

Can keep an eye on disk usage when experimenting?

What is your disk layout?  How much free disk space is on the volume 
containing the directory of input images before stitching?  how much after 
successfully stitching with a single core?

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

Title:
  Stitching fails with multiple cores

Status in Hugin - Panorama Tools GUI:
  New

Bug description:
  Stitching fails when two cpu cores available as per attachment:

  If I load windows with only one core available (/onecpu switch)
  stitching always succeeds.

  Windows XP Pro SP3 – GeForce 9600GT – Drv Nvidia 275.33
  Hugin 2011.0.0.0fd3e119979c

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