Displaying 20 results from an estimated 26 matches for "runlast".
Did you mean:
runas
2020 Nov 23
2
.Internal(quit(...)): system call failed: Cannot allocate memory
...b") at sysutils.c:311
311 {
(gdb) where
#0 R_system (command=command at entry=0x7fffffffa1e0 "rm -Rf
/tmp/RtmppoKPXb") at sysutils.c:311
#1 0x00005555557c30ec in R_CleanTempDir () at sys-std.c:1178
#2 0x00005555557c31d7 in Rstd_CleanUp (saveact=<optimized out>, status=0,
runLast=<optimized out>) at sys-std.c:1243
#3 0x00005555557c593d in R_CleanUp (saveact=saveact at entry=SA_NOSAVE,
status=status at entry=0, runLast=<optimized out>) at system.c:87
#4 0x00005555556cc85e in do_quit (call=<optimized out>, op=<optimized
out>, args=0x555557813f90, rho...
2020 Nov 21
4
.Internal(quit(...)): system call failed: Cannot allocate memory
...opers,
Some of the more fat scripts (50+ GB mem used by R) that I am running,
when they finish they do quit with q("no", status=0)
Quite often it happens that there is an extra stderr output produced
at the very end which looks like this:
Warning message:
In .Internal(quit(save, status, runLast)) :
system call failed: Cannot allocate memory
Is there any way to avoid this kind of warnings? I am using stderr
output for detecting failures in scripts and this warning is a false
positive of a failure.
Maybe quit function could wait little bit longer trying to allocate
before it raises this...
2001 Jan 17
4
Can one set --no-save in .Rprofile
(On Unix/Linux)
Is it possible to set the --no-save command line option as an option
in the .Rprofile file. I have looked in the sources and do not see
any obvious (user initiated) ways of changing the command line defaults,
but I am hoping I have missed something.
I *know* I can write my own shell script wrapper that calls R with
whatever arguments I want (and I do that). However there
2011 Jun 02
1
Exiting R Gracefully
...age? [y/n/c]: n
*** caught segfault ***
address (nil), cause 'unknown'
Possible actions:
1: abort (with core dump, if enabled)
2: normal R exit
3: exit R without saving workspace
4: exit R saving workspace
Selection: 3
Error: no graphics system to unregister
>
> q("no", runLast = FALSE)
Error in q("no", runLast = FALSE) : no graphics system to unregister
--------------------------------------
Dario Strbenac
Research Assistant
Cancer Epigenetics
Garvan Institute of Medical Research
Darlinghurst NSW 2010
Australia
2020 Nov 24
2
.Internal(quit(...)): system call failed: Cannot allocate memory
...>> (gdb) where
>> #0 R_system (command=command at entry=0x7fffffffa1e0 "rm -Rf /tmp/RtmppoKPXb") at sysutils.c:311
>> #1 0x00005555557c30ec in R_CleanTempDir () at sys-std.c:1178
>> #2 0x00005555557c31d7 in Rstd_CleanUp (saveact=<optimized out>, status=0, runLast=<optimized out>) at sys-std.c:1243
>> #3 0x00005555557c593d in R_CleanUp (saveact=saveact at entry=SA_NOSAVE, status=status at entry=0, runLast=<optimized out>) at system.c:87
>> #4 0x00005555556cc85e in do_quit (call=<optimized out>, op=<optimized out>, args=0...
2013 Apr 10
1
problem quitting
...r-project.org
> Reply-To: r-help at r-project.org
> On Apr 3, 2013, at 23:58 , Julian Wells wrote:
>
>> Can someone explain why all of a sudden I can't quit?
>
> Almost certainly because you have a .Last function that fails. Either get rid of it, or try q("n", runLast=FALSE).
>
> -pd
> ------------------------------
>
> Message: 6
> Date: Thu, 04 Apr 2013 12:33:24 +0100
> From: Prof Brian Ripley <ripley at stats.ox.ac.uk>
> To: r-help at r-project.org
> Subject: Re: [R] Problem quitting
> Message-ID: <515D6504.4070102 at...
2004 May 31
1
e1071 build issue
...9;
Delete downloaded files (y/N)? y
Warning message:
Installation of package e1071 had non-zero exit status in:
install.packages("e1071")
> library(e1071)
Error in library(e1071) : There is no package called 'e1071'
> quit
function (save = "default", status = 0, runLast = TRUE)
.Internal(quit(save, status, runLast))
<environment: namespace:base>
2007 Nov 27
1
recovering "status" after q(status=n) in Windows
...package:base R Documentation
>
> Terminate an R Session
>
> Description:
>
> The function 'quit' or its alias 'q' terminate the current R
> session.
>
> Usage:
>
> quit(save = "default", status = 0, runLast = TRUE)
> q(save = "default", status = 0, runLast = TRUE)
> .Last <- function(x) { ...... }
>
> Arguments:
>
> save: a character string indicating whether the environment
> (workspace) should be saved, one of '"no"', ...
2020 Nov 24
0
.Internal(quit(...)): system call failed: Cannot allocate memory
...1
> 311 {
> (gdb) where
> #0 R_system (command=command at entry=0x7fffffffa1e0 "rm -Rf /tmp/RtmppoKPXb") at sysutils.c:311
> #1 0x00005555557c30ec in R_CleanTempDir () at sys-std.c:1178
> #2 0x00005555557c31d7 in Rstd_CleanUp (saveact=<optimized out>, status=0, runLast=<optimized out>) at sys-std.c:1243
> #3 0x00005555557c593d in R_CleanUp (saveact=saveact at entry=SA_NOSAVE, status=status at entry=0, runLast=<optimized out>) at system.c:87
> #4 0x00005555556cc85e in do_quit (call=<optimized out>, op=<optimized out>, args=0x5555578...
2020 Nov 25
1
[External] Re: .Internal(quit(...)): system call failed: Cannot allocate memory
...t;>>> #0 R_system (command=command at entry=0x7fffffffa1e0 "rm -Rf /tmp/RtmppoKPXb") at sysutils.c:311
>>>> #1 0x00005555557c30ec in R_CleanTempDir () at sys-std.c:1178
>>>> #2 0x00005555557c31d7 in Rstd_CleanUp (saveact=<optimized out>, status=0, runLast=<optimized out>) at sys-std.c:1243
>>>> #3 0x00005555557c593d in R_CleanUp (saveact=saveact at entry=SA_NOSAVE, status=status at entry=0, runLast=<optimized out>) at system.c:87
>>>> #4 0x00005555556cc85e in do_quit (call=<optimized out>, op=<optimized...
2020 Nov 24
0
.Internal(quit(...)): system call failed: Cannot allocate memory
...where
> >> #0 R_system (command=command at entry=0x7fffffffa1e0 "rm -Rf /tmp/RtmppoKPXb") at sysutils.c:311
> >> #1 0x00005555557c30ec in R_CleanTempDir () at sys-std.c:1178
> >> #2 0x00005555557c31d7 in Rstd_CleanUp (saveact=<optimized out>, status=0, runLast=<optimized out>) at sys-std.c:1243
> >> #3 0x00005555557c593d in R_CleanUp (saveact=saveact at entry=SA_NOSAVE, status=status at entry=0, runLast=<optimized out>) at system.c:87
> >> #4 0x00005555556cc85e in do_quit (call=<optimized out>, op=<optimized out&g...
2004 May 05
1
Ctrl-C with R.exe and Rterm.exe in R v1.9.0
...ognized as an internal or external command,
operable program or batch file.
C:\Program Files\R>1+1
'+1' is not recognized as an internal or external command,
operable program or batch file.
C:\Program Files\R>q
C:\Program Files\R>
function (save = "default", status = 0, runLast = TRUE)
.Internal(quit(save, status, runLast))
<environment: namespace:base>
>
Clearly both cmd.exe and R is trying to parse the stdin. Some
keystrokes goes to R and some to cmd.exe.
Best wishes
Henrik Bengtsson
Div. of Mathematical Statistics @ Centre for Mathematical Sciences
Lund In...
2009 May 04
4
Surface for R outside of R
Hi all,
i am new here and this is my first posting. My coding experience in R ist
okay, but I have a problem which is related to another aspect of R.
I am searching for a surface which execute my commands in R via a click on a
button OUTSIDE of R. Concrete: I will write some programs in R and want to
execute this files outside of R, so I don't want to start R eyery time if i
want an
2020 Nov 23
0
.Internal(quit(...)): system call failed: Cannot allocate memory
...scripts (50+ GB mem used by R) that I am running,
> when they finish they do quit with q("no", status=0)
> Quite often it happens that there is an extra stderr output produced
> at the very end which looks like this:
>
> Warning message:
> In .Internal(quit(save, status, runLast)) :
> system call failed: Cannot allocate memory
>
> Is there any way to avoid this kind of warnings? I am using stderr
> output for detecting failures in scripts and this warning is a false
> positive of a failure.
>
> Maybe quit function could wait little bit longer trying...
2018 Apr 27
0
Package ddalpha is not building for me in R 3.5.0
...ch=", :
cannot popen ' '/usr/local/lib64/R/bin/R' --no-save --slave 2>&1 <
'/tmp/RtmpZB2yyH/file64c65776e871'', probable reason 'Cannot allocate
memory'
* removing ?/usr/local/lib64/R/library/ddalpha?
Warning in q("no", status = status, runLast = FALSE) :
system call failed: Cannot allocate memory
> sessionInfo()
R version 3.5.0 Patched (2018-04-23 r74633)
Platform: x86_64-pc-linux-gnu (64-bit)
Running under: Slackware 14.2 x86_64 (post 14.2 -current)
Matrix products: default
BLAS: /usr/local/lib64/R/lib/libRblas.so
LAPACK: /usr/l...
2010 Jan 10
0
commandArgs return value
...gs[3]), sep = " "), sep = "\n")
ix = grep("--arg", args, fixed = TRUE)
if (ix < length(args)){
for (i in (ix+1):length(args)) {
cat(paste("argument #",i-ix,"-->",args[i], sep=" "), sep = "\n")
}
}
ecode = 0
q(runLast = FALSE, save = "no", status = ecode)
###### script end
###### output file begin
All the arguments...
/Library/Frameworks/R.framework/Resources/bin/exec/i386/R
-f
/Users/Shared/code/R/hbb/pam/script.r
--restore
--save
--no-readline
--slave
--vanilla
--args
dogs
cats
verbose=TRUE
nargs...
2010 Apr 18
2
how to use Excel VBA's Shell() to call and execute R file
I have an R file R_test.R saved in C:\R_test folder. The R_test.R looks like
this:
setwd("C:/R_test")
rnorm(100)
write(rnorm(100),"data.txt")
q(save="no", runLast = F)
Next I would like use an Excel VBA/macro Shell() function to call R and
execute R_test.R file. The syntax is *Shell(pathname*[*,windowstyle*]*)*
I wrote an Excel macro RunRcode like this:
Sub RunRcode()
Dim RetVal
RetVal = "C:\Program Files\R\R-2.10.1\bin\Rgui.exe & C:\R_test...
2007 Feb 27
1
Problem with R interface termination
Dear Sir,
The R interface that i am currently using is R 2.4.1( in Win XP). I am not able to terminate the program by giving the q() command. Each time I pass this command,
> q()
Error in .Last() : could not find function "finalizeSession"
this error creeps in and it neither allows me to save my workspace nor come out of R. Therefore, whenever this happens, I am forced to end the
2000 Mar 16
2
R-1.0.0 on alpha/osf1 memory glitch (PR#490)
Digital Alpha (various), Digital UNIX V4.0[EF], R-1.0.0, gcc, f77
When using batch mode with the save option, an error message is issued.
However [I have just discovered that] it appears that the operation
does complete, i.e. the .RData file is saved successfully. The main
problem is that the return code is non-zero (and so it is impossible to
distinguish this "non-error" from some
2003 Aug 24
1
declarations in non-exported headers and embedding R
...E,
SA_SAVE,
SA_SAVEASK,
SA_SUICIDE
} SA_TYPE;
-------------------------------------------------------------
from non-exported header file ${R_HOME}/src/unix/Runix.h
-------------------------------------------------------------
extern void Rstd_CleanUp(SA_TYPE saveact, int status, int runLast);
Use:
-------------
When the PostgreSQL backend process exits, Rstd_CleanUp() is called via
registered onexit callback so that the embedded R interpreter can clean
up (e.g. to remove the created Rtmp[pid] directory).
Note:
-------------
Similar use found in ${R_HOME}/tests/Embedding/Rerror.c