Hi,
the strange thing is that I don't see the leak when I run moses in valgrind.
Valgrind makes the process run much slower, which might explain the problem.
What I see in valgrind is a stable usage of 7.5G of memory up until sentence
130 (where I stopped the process, and valgrind reported a m
Hi Evgeny
I've tried to reproduce the mem leak with distinct n-best, I don't see a
problem.
are you able to run valgrind and see where the leak is coming from?
Evgeny Matusov wrote:
> Hi,
>
> I tried to run Moses to produce N-best lists with distinct hypotheses
> (setting -nbest-list 500 dist
Hi,
I tried to run Moses to produce N-best lists with distinct hypotheses
(setting -nbest-list 500 distinct). Although I also set
"-use-persistent-cache false", the memory usage continues to grow from
sentence to sentence during translation. The memory consumption drops only
2-3 times in the firs
Hi,
I tried to run Moses to produce N-best lists with distinct hypotheses
(setting -nbest-list 500 distinct). Although I also
set "-use-persistent-cache false", the memory usage continues to grow from
sentence to sentence during translation. The memory consumption drops only
2-3 times in the
