On Jan 12, 10:44 am, Lukáš Jirkovský <[email protected]> wrote: > > Oh, I have misunderstood first time. I thought you were talking about > enblend/enfuse image cache. > > Is the limit correctly set in preferences after restart? > > Anyway I took a look at the code and I don't see any limits here (OK, > it seems there is limit to 2048TB). I can't find any limit which could > cause this. Currently I can think only about one cause and it's some > setting in /etc/security/limits.conf (If it's here, I remember > Slackware 10(or 9?) didn't use it). I've never tried any of the memory > related setting though... Of course it may be some strange kernel option > so I'd browse through /proc if the former doesn't help. > > Lukas
I don't think it's a kernel or security limitation because I've had enblend/enfuse go up to 16-20G in size before, at least that's what top reports. If I go into preferences and set the number to 2047 and click apply everything stays. If I go up just 1 to 2048 and click Apply the box resets itself to 1. Just found something interesting. If I go into the hugin config file (.hugin) and adjust the cache size - here's where it started: [ImageCache] Mapping=1 UpperBound=2146435072 If I change UpperBound to say 3146435072 and start up hugin and go to preferences, it shows fine, roughly 3G cache. But if I click Apply, then it gets reset to 1. Could it be something in the interface code or wxwidgets that's causing this?
-- 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
