Fixed a significant OutOfMemoryError on default.

12 views
Skip to first unread message

burtonator

unread,
May 8, 2012, 6:26:13 PM5/8/12
to peregrine...@googlegroups.com
The problem manifests itself on larger jobs... but it's fixed now.

I'm trying to make sure all tests pass on LARGE amounts of data, not just smaller amounts.

Hopefully it will be working soon... 

Kevin

Roland Gude

unread,
May 10, 2012, 12:20:17 PM5/10/12
to peregrine...@googlegroups.com
I found another Memory leak and fixed it (i suppose), but i am not 100% sure about implications of the fix see issue https://bitbucket.org/burtonator/peregrine/issue/64/memory-leak-in-basetaskrpcdelegate.

Roland Gude

unread,
May 15, 2012, 5:08:40 PM5/15/12
to peregrine...@googlegroups.com
I suspect another memory leak during Reduce, but i cannot wrap my head around it. can i send you a heap dump from a run that produced an OOM with >500M heap retained by a single Reduce thread?

burtonator

unread,
May 28, 2012, 5:47:04 PM5/28/12
to peregrine...@googlegroups.com
I just fixed one due to the fact that we weren't setting the right memlock limit... I'll post about it now.

Kevin
Reply all
Reply to author
Forward
0 new messages