I am running R2.4.1 under Windows.> version_ platform i386-pc-mingw32 arch i386 os mingw32 system i386, mingw32 status major 2 minor 4.1 year 2006 month 12 day 18 svn rev 40228 language R version.string R version 2.4.1 (2006-12-18)>Sometimes when I exit R I do it by right clicking on the Windows tab for the group of R processes that are running (I am running in SDI mode) so there is usually the GUI and a graphics window open. When I choose the option to close the group, the tab disappears indicating that the processes have been exited, but I get the CPU going to 100% utilization. Opening the windows Task Manager I see that the RGui process is the one consuming all the CPU. I then "end" the process with the Task Manager and everything is fine. I have not noticed that problem when either I "q()" or close the RGui window. I was wondering if anyone else has seen the problem, or might there be something wrong with my configuration. I guess that I will just have to be nice and do "q()" to get out of the session. -- Jim Holtman Cincinnati, OH +1 513 646 9390 What is the problem you are trying to solve?
On 1/27/2007 11:53 PM, jim holtman wrote:> I am running R2.4.1 under Windows. > >> version > _ > platform i386-pc-mingw32 > arch i386 > os mingw32 > system i386, mingw32 > status > major 2 > minor 4.1 > year 2006 > month 12 > day 18 > svn rev 40228 > language R > version.string R version 2.4.1 (2006-12-18) > > Sometimes when I exit R I do it by right clicking on the Windows tab > for the group of R processes that are running (I am running in SDI > mode) so there is usually the GUI and a graphics window open. When I > choose the option to close the group, the tab disappears indicating > that the processes have been exited, but I get the CPU going to 100% > utilization. > > Opening the windows Task Manager I see that the RGui process is the > one consuming all the CPU. I then "end" the process with the Task > Manager and everything is fine. I have not noticed that problem when > either I "q()" or close the RGui window. > > I was wondering if anyone else has seen the problem, or might there be > something wrong with my configuration. I guess that I will just have > to be nice and do "q()" to get out of the session.I haven't seen this before, but I don't usually close R that way. I just tried it in R-devel (by starting R, opening 10 plot windows so the taskbar buttons collapsed into one, and clicking on "close group"), and I got a crash. I'll look into it. Duncan Murdoch
Possibly Parallel Threads
- changing dir. to network drive crash Rgui on NT4 ( PR#282 8)
- Creating a graphics window (in Windows, with RGui) that is not constrained to the RGui Window
- Potential minor GUI bug
- Memory increase in R
- Compiling R on Windows XP - Rgui crashes yet Rterm works