<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Ok, should be fixed in r823 just committed.<div><br></div><div>Let me know if the problem persist<br><div><br><div><div>On Dec 7, 2011, at 11:13 AM, Yury Aulchenko wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I think this is something I introduced in rev. 810-814 (a new without delete). Now (hopefully) fixed, will commit changes in next hour.<br><div>
<span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>-------------------------------------------------------</div><div>Yurii Aulchenko, PhD, Dr. Habil.</div><div>Independent researcher and consultant</div><div>yurii [dot] aulchenko [at] gmail [dot] com</div></div></div></span></div></span></span>
</div>
<br><div><div>On Dec 7, 2011, at 11:03 AM, L.C. Karssen wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Dear list,<br><br>We just tried to convert a GenABEL object to plink format using export.plink() from GenABEL v 1.7-0 (still under development, package built from SVN yesterday), and it nearly brought the machine to a halt because it used all available memory (RAM + swap).<br><br>Our GenABEL object contained almost 3700 individuals and about 700k SNPS.<br><br>Have others experienced this as well? I haven't looked at Yurii's latest implementation of the function in C++ yet. Hopefully I will be able to find some time later today. Does anyone here know how we could limit memory usage in C++?<br><br><br>Thanks,<br><br>Lennart.<br></div></blockquote></div></div></blockquote></div><br></div></div></body></html>