[R-SIG-Mac] R 3.1.2 & Yosemite GUI slowness

[Simon Urbanek]

Thank you both, I'll look into this as soon as I get back from travels.
Simon


On Feb 23, 2015, at 4:23 PM, David Dobolyi <dd2es at virginia.edu> wrote:

> Dear Simon,
> 
> Thank you for your reply. I am using the Mavericks build (running on latest Yosemite), and have noticed this issue ever since I upgraded to 3.1.2:
> 
> <Screen Shot 2015-02-23 at 4.12.35 PM.png>
> 
> As an aside, I occasionally see errors in the GUI like this, and they seem to come from other apps (e.g., Dropbox):
> 
> <Screen Shot 2015-02-23 at 4.13.09 PM.png>
> 
> More importantly, I wrote Yan about a workaround, which involves changing the max.print option from the default and limiting it to 1000. This reliably stops R from slowing down over time (although how long, I don't know). However, I can replicate the basic issue easily in R with the following code:
> 
> options(max.print=99999)
> temp <- data.frame(1:100000, 1:100000)
> temp
> 
> This should eventually turn up on screen, and after try typing anything in the console. Typing will be extremely delayed (e.g., type hello and it will take several seconds for each letter to show up, one at a time).
> 
> It's even possible to crash the GUI if you print something in a function called in a bootstrap, and then invoke a progress bar (e.g., the pROC package). Progress will be steady and then suddenly R will lock up. The moment you remove the print statement (which isn't actually printing since the progress bar is present), the same call works perfectly.
> 
> I'd love to have a real fix for this other than reducing max.print. I'd dig into the source myself but can't commit the time at the moment.
> 
> Best,
> 
> David
> 
> 
> 
> On Mon, Feb 23, 2015 at 4:00 PM, Simon Urbanek <simon.urbanek at r-project.org> wrote:
> Are you using the Mavericks build of R? The SL build will do that, because SL has no AppNap support - but then you can also disable AppNap (see the corresponding threads here).
> 
> Cheers,
> S
> 
> 
> On Feb 14, 2015, at 12:43 AM, David Dobolyi <dd2es at virginia.edu> wrote:
> 
> > Dear Yan,
> >
> > Are you still seeing this issue? It has been bothering me for months now,
> > and I even found an instance where using progress_bar with underlying
> > output to the GUI will cause so much slowdown as to crash R given
> > sufficient time (i.e., as hidden printed output piles
> > up in the background, the whole process slows to a crawl).
> >
> > Best,
> >
> > David
> >
> > _______________________________________________
> > R-SIG-Mac mailing list
> > R-SIG-Mac at r-project.org
> > https://stat.ethz.ch/mailman/listinfo/r-sig-mac
> >
> 
> 
> 
> 
> -- 
> David Dobolyi, M.A.
> PhD Candidate
> Cognitive Psychology
> University of Virginia
> 434-535-6073
> dd2es at virginia.edu