[R-SIG-Mac] R 2.2.1/Cocoa - internal editor cpu/mem leaks; external editor call doesn't work

JBThiel jbthiel at neticare.com
Fri Feb 17 04:45:48 CET 2006


R 2.2.1   on OS X  10.4.3   (also seen on OS X 10.3.9)
via the Cocoa GUI:


* The R internal editor rails the cpu to 100% when open, even when it  
is just sitting in the background -- probably is using polling.

* There appears to be a memory leak with the internal editor, whereby  
every time the editor is loaded and exited, the R app consumes at  
least 1.2MB of additional memory, and fails to release it.   A simple  
cycle of:
	loop:
		fix(abc)
		close the edit window

will apparently increase the R real memory allocation without bound.


* Possibly related to the above, as the internal editor is invoked  
repeatedly over time, it takes increasingly longer to load the edit  
window.


* We have also observed a condition where simply mouse-click  
switching between the Rconsole window and another R window containing  
a displayed graph - but not actually doing anything other than  
clicking back and forth,  increases the R real memory usage by  
10-20KB on each series of clicks.

* Editing via external editor does not seem to work.  The fix() call  
invokes the external application, but returns immediately.  The  
external editor starts up fine, and sees the tempfile, but any  
editing done to it is never seen  (since the fix() has already  
returned).   Tested with editors like TextWrangler, Smultron, TextEdit.


These bugs make it problematic to run long R sessions with heavy  
editing, as the R session starts to drag more and more   (and can   
induce other application (possibly even system) crashes as other apps  
fail to run in the diminishing memory space).

Thanks for your great work on the Cocoa R, which is extremely useful  
to us.

Best regards,

John



More information about the R-SIG-Mac mailing list