From 184523479 at qq.com  Tue Jul 16 20:07:34 2013
From: 184523479 at qq.com (ge11232002)
Date: Tue, 16 Jul 2013 11:07:34 -0700 (PDT)
Subject: [Rd] Read a text file into R with .Call()
In-Reply-To: <AD0DBA87-8945-49E4-A3FE-792AD33FD4E3@r-project.org>
References: <tencent_1039840B6669131118B8D10B@qq.com>
	<tencent_541DA6027020FB783AB8DC58@qq.com>
	<AD0DBA87-8945-49E4-A3FE-792AD33FD4E3@r-project.org>
Message-ID: <1373998039892-4671704.post@n4.nabble.com>

Hi Simon,

I am sorry that for some unknown reasons I did not receive your reply on 27
June 2013 in my email boxs. I just randomly searched and read it today on
Nabble.
Thank you for your explaination and it really helps me to understand how the
memory allocation works.

One more short questions is
If the "resident" memory from top or ps can be misleading, then how can I
detect the memory leak happening in the .Call()? Is the leaked memory
visible in the gc()? or it can be detected by mallinfo() from your mallinfo
package?

Thanks again!
Ge
 



--
View this message in context: http://r.789695.n4.nabble.com/Read-a-text-file-into-R-with-Call-tp4670443p4671704.html
Sent from the R devel mailing list archive at Nabble.com.



[Rd] Read a text file into R with .Call()
ge11232002