Harry,
Maybe I should reply in this thread. I have used strace to trace what's going on. My analysis is that enblend suddenly goes from normal to crazy. In crazy mode, it does nothing but allocate memory until exhausted. On 32bit OSes it fails after allocating around 3G of adressing space, on my 64bit system it runs a few milliseconds longer, and allocates more than 12Gb before running out of something..... enblend was started with no -m option, equivalent to -m 1024, so it shouldn't allocate more than about 1Gb of memory. until the error situation, this works fine, and it runs with whatever you tell it to. To me it looks as if someone wrote a loop to try again if the malloc fails. And somehow this loop takes the valid return as "semi-failed" and tries again, until it really fails. Roger. On May 8, 1:55 am, grow <[email protected]> wrote: > I ran the new RC1-dmalloc version with the problematic project and > had what looks to me like "the usual" crash. The error report is > below. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx -~----------~----~----~----~------~----~------~--~---
