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 <file> 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 first 100 sentences as opposed to after every sentence. 
> After 100 to 150 sentences, the program dies with bad_alloc.
>
> Do you know what causes this problem?
>
> I run this on a task with about 700K sentence pairs (GALE-type data), setting 
> stack size to 100, stack diversity to 10 and max-trans-opt-per-coverage to 
> 15, and had no problems running translation with single-best output only.
>
>
> Thanks much,
> Evgeny.
>
> P.S. I just found that this issue had been discussed and presumably fixed 
> sometime ago; however, I still have this problem with the latest svn commit 
> of Moses.
>
>   
_______________________________________________
Moses-support mailing list
[email protected]
http://mailman.mit.edu/mailman/listinfo/moses-support

Reply via email to