Hi Stefan,
2009/10/8 Stefan Peter s_pe...@swissonline.ch:
Hi List,
Sorry if the following is all known by the old hands. Please feel free
to correct me at your leisure, otherwise I may die dumb ;)
I have downloaded the project in question, and here are some results.
I used Hugin
2009/10/7 Harry van der Wolf hvdw...@gmail.com:
I did another run from the Gui (took a few minutes to find how to compile
that one). That gave more results:
I didn't know that there is a GUI for it.
[assemble.h:308]: (possible style) Pre-Incrementing variable 'i' is
preferred to
2009/10/7 Stefan Peter s_pe...@swissonline.ch:
Hi Lukáš
instead of changing the RAM on your PC, you could use a virtual machine
like vmware or virtualbox. There, you can limit the resources at your will.
Regards
Stefan Peter
Hi Stefan,
I know about this option but I thing changing
2009/10/8 Lukáš Jirkovský l.jirkov...@gmail.com
2009/10/7 Harry van der Wolf hvdw...@gmail.com:
I did another run from the Gui (took a few minutes to find how to compile
that one). That gave more results:
I didn't know that there is a GUI for it.
cd into the gui directory and run
2009/10/8 Harry van der Wolf hvdw...@gmail.com:
2009/10/8 Lukáš Jirkovský l.jirkov...@gmail.com
2009/10/7 Harry van der Wolf hvdw...@gmail.com:
I did another run from the Gui (took a few minutes to find how to
compile
that one). That gave more results:
I didn't know that there is a
I downloaded the git from danmar_cppcheck
2009/10/8 Lukáš Jirkovský l.jirkov...@gmail.com
2009/10/8 Harry van der Wolf hvdw...@gmail.com:
2009/10/8 Lukáš Jirkovský l.jirkov...@gmail.com
2009/10/7 Harry van der Wolf hvdw...@gmail.com:
I did another run from the Gui (took a few
I've tried to reproduce the bug but without success.
I've remapped images. Enblend usually takes about 2-3 GB of memory
with this pano. I lowered RAM to 256MB and swap from 512MB to 195MB.
(KDE takes about 200MB itself). I've run enblend with: -m 200 -b 8196
to expose the bug even earlier. After
Am Thursday 08 October 2009 schrieb Lukáš Jirkovský:
I've tried to reproduce the bug but without success.
I've remapped images. Enblend usually takes about 2-3 GB of memory
with this pano. I lowered RAM to 256MB and swap from 512MB to 195MB.
(KDE takes about 200MB itself). I've run enblend
Hi List,
Sorry if the following is all known by the old hands. Please feel free
to correct me at your leisure, otherwise I may die dumb ;)
I have downloaded the project in question, and here are some results.
I used Hugin 2009.2.0.4461 on linux X86_64 with 4GB Memory and 8 GB swap
for the
Hi
I'd be interested in doing some tests, too. I remember having had memory
issues as well, but I was never able to reproduce them reliably here on
Linux / Linux_64 and Windows. Is there someplace one could get the
project in question?
Cheers
Stefan Peter
To answer my own mail. :-)
I just compiled cppcheck on OSX and did a standard run on the enblend trunk.
It displays the following
[./vigra_impex/jpeg.cxx:132]: (error) Class JPEGCodecImpl which is inherited
by class JPEGDecoderImplBase does not have a virtual destructor
Hi Harry,
2009/10/7 Harry van der Wolf hvdw...@gmail.com:
2009/10/7 Lukáš Jirkovský l.jirkov...@gmail.com
I'm not Mac user (although I find it really cool but very expensive)
but I may found solution for out of memory problem. I had a discussion
about memory and I mentioned these
I did another run from the Gui (took a few minutes to find how to compile
that one). That gave more results:
[assemble.h:308]: (possible style) Pre-Incrementing variable 'i' is
preferred to Post-Incrementing
[assemble.h:308]: (possible style) Pre-Incrementing variable 'i' is
preferred to
Hi Lukáš
instead of changing the RAM on your PC, you could use a virtual machine
like vmware or virtualbox. There, you can limit the resources at your will.
Regards
Stefan Peter
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the
14 matches
Mail list logo
