similar to: Garbage collector crashes after calling a C function

Displaying 20 results from an estimated 800 matches similar to: "Garbage collector crashes after calling a C function"

2019 Feb 27
2
Intermittent crashes with inset `[<-` command
Valgrind (without gctorture) reports memory misuse: % R --debugger=valgrind --debugger-args="--leak-check=full --num-callers=18" ... > x <- 1:200000 > y <- rep(letters[1:5], length(x) / 5L) > for (i in 1:1000) { + # x[y == 'a'] <- x[y == 'b'] + x <- `[<-`(x, y == 'a', x[y == 'b']) + cat(i, '') + } 1 2 3 4 5 6 7 8 9 10
2019 Feb 26
8
Intermittent crashes with inset `[<-` command
The following code crashes after about 300 iterations on my?x86_64-w64-mingw32?machine on R 3.5.2 --vanilla.?? Others have duplicated this (see?https://github.com/tidyverse/magrittr/issues/190?if necessary), but I don't know how machine/OS-dependent it may be.?? If it doesn't crash for you, please try increasing the length of the x vector. Substituting the commented-out line for the one
2007 Jun 21
2
segfault during cbind
The following code results in a seg fault. > sessionInfo() R version 2.6.0 Under development (unstable) (2007-06-21 r42013) x86_64-unknown-linux-gnu locale: LC_CTYPE=en_US;LC_NUMERIC=C;LC_TIME=en_US;LC_COLLATE=en_US;LC_MONETARY=en_US;LC_MESSAGES=en_US;LC_PAPER=en_US;LC_NAME=C;LC_ADDRESS=C;LC_TELEPHONE=C;LC_MEASUREMENT=en_US;LC_IDENTIFICATION=C attached base packages: [1] stats graphics
2002 Nov 11
2
R 1.6.1: help with debugging error in RunGenCollect(), R_gc_internal
Hi, [System info: R 1.6.1 compiled from source (no args to configure) on Redhat 7.1 Linux i/386] I have some spatial statistics programs that recently (since R 1.6.1) have generated SIGSEGV. These R programs use the splancs library as well as some C code of my own for Voronoi analysis. The program has a big loop to fit various model parameters against a spatial distribution of biological
2006 Oct 19
0
Memory leak
This is a followup to the R-help thread, "Error: STRING_ELT() can only be applied to a 'character vector', not a 'builtin'". Thanks to Prof. Brian Ripley for suggesting the use of gctorture and valgrind. I am getting segmentation faults that appear to come from a memory leak. I now have a reproducible example (below). It requires the "g.data" package
2007 Feb 21
2
R unstable and crashes after executing .C
Dear R listers, I have developed a C function to be executed from R through the ".C" interface. After doing dyn.load, the function executes properly and I get the results. However, after executing my function, R seems to get unstable and crashes (giving a segmentation fault and exiting) whenever I try to do ANYTHING with a relatively large object (creating a new one or even just
2019 Feb 27
0
Intermittent crashes with inset `[<-` command
On an azure centos VM, I can reproduce this bug which reports either: *** caught segfault *** address 0x70000006a, cause 'memory not mapped' (crash) Or incompatible types (from builtin to integer) in subassignment type fix (no crash) Like Gabriel, I could not reproduce the bug on a mac laptop. Both R versions 3.5.1. Travers On Wed, Feb 27, 2019 at 9:08 AM William Dunlap via R-devel
2012 May 30
1
Automatically install package dependencies
Hi, I have a R Package. It is working, but I can't that it install the dependencies automatically. When I try to install I receive this message: > install.packages("./RT4Bio_1.0.tar.gz",dependencies=TRUE) Installing package(s) into '/usr/local/lib/R/site-library' (as 'lib' is unspecified) inferring 'repos = NULL' from the file name ERROR: dependency
2003 Apr 21
0
sweave provoked segfault (PR#2809)
This problem is with R 1.7.0 (as released) on Linux and Solaris. Details below are from Linux, Mandrake 9.1. The problem also happened with R 1.6.2 and on Mandrake 9.0. Vignettes often (for me) provokes problems with the misleading error message: * creating vignettes ... ERROR Error in sub(pattern, replacement, x, ignore.case, extended) : invalid argument Error in buildVignettes(dir =
2004 Sep 13
6
Spare some CPU cycles for testing lme?
If anyone has a few extra CPU cycles to spare, I'd appreciate it if you could verify a problem that I have encountered. Run the code below and tell me if it crashes your R before completion. library(lme4) data(bdf) dump<-sapply( 1:50000, function(i) { fm <- lme(langPOST ~ IQ.ver.cen + avg.IQ.ver.cen, data = bdf, random = ~ IQ.ver.cen | schoolNR); cat("
2002 Jun 12
3
help debugging segfaults
(Sorry for the cross-post--- I wasn't sure which list is more appropriate...) Hi everyone, I've run into segfaults when using my randomForest package on large dataset (e.g., 100 x 15200) and large number of trees (e.g., ntree=7000 and mtry=3000). I'm wondering if anyone can give me some hints on where to look for the problem. The randomForest package mainly consists of two things:
2002 Jun 12
3
help debugging segfaults
(Sorry for the cross-post--- I wasn't sure which list is more appropriate...) Hi everyone, I've run into segfaults when using my randomForest package on large dataset (e.g., 100 x 15200) and large number of trees (e.g., ntree=7000 and mtry=3000). I'm wondering if anyone can give me some hints on where to look for the problem. The randomForest package mainly consists of two things:
2001 Jan 23
0
1.2.1 segfault
I've trapped this segfault with gdb, but I'm not sure what it means or what to do next. Paul _____ $ R -d gdb GNU gdb 4.17 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is
2001 Jul 02
0
ReleaseLargeFreeVectors SIGSEGV (?) (PR#1008)
Full_Name: Roger Bivand Version: 1.3.0 OS: GNU/Linux RH6.2, 7.0, Debian 2.2 Submission from: (NULL) (158.37.100.64) I'm working on interfacing ANN: A Library for Approximate Nearest Neighbor Searching (http://www.cs.umd.edu/~mount/ANN/) to R, following up a prototype package I tried in May 2000. ANN is written in C++; my C++ is very weak. Last year I didn't experience any problems with
2015 Jun 13
2
Lack of protection bug in current R release candidate
The current R release candidate has a lack of protect bug (of very long standing) with respect to the R_print.na_string and R_print.na_string_noquote fields of the static R_print structure declared in Print.h. This shows up very occassionally as incorrect output from the following lines in reg-tests-2.R: x <- c("a", NA, "b") factor(x) factor(x, exclude="")
2011 Aug 26
2
read.table segfaults
> fil2s <- read.table("../Data/fil2_s.txt", header = FALSE, sep = "\t") Program received signal SIGSEGV, Segmentation fault. 0x000000000041c2e1 in RunGenCollect (size_needed=8192000) at memory.c:1514 1514 PROCESS_NODES(); (gdb) > sessionInfo() R version 2.13.1 Patched (2011-08-25 r56798) Platform: x86_64-unknown-linux-gnu (64-bit) locale: [1]
2018 Nov 07
5
XPS 13 9370 / CentOS compat
Am 07.11.2018 um 15:15 schrieb Jim Perrin <jperrin at centos.org>: > > On 11/3/18 12:32 PM, Leon Fauster via CentOS wrote: >> Anyone with some Dell laptop XPS 13 9370 (2018) experience here? >> Especially with that "Killer 1435 (802.11ac 2x2 und Bluetooth)" device? >> Supported by the stock kernel (EL7)? > > > I had reasonably unreliable
2007 Feb 21
1
R unstable and crashes after executing .C
Dear R listers, I have developed a C function to be executed from R through the ".C" interface. After doing dyn.load, the function executes properly and I get the results. However, after executing my function, R seems to get unstable and crashes (giving a segmentation fault and exiting) whenever I try to do ANYTHING with a relatively large object (creating a new one or even just writing
2018 Nov 03
2
XPS 13 9370 / CentOS compat
Anyone with some Dell laptop XPS 13 9370 (2018) experience here? Especially with that "Killer 1435 (802.11ac 2x2 und Bluetooth)" device? Supported by the stock kernel (EL7)? -- Thanks, LF
2001 Feb 20
2
segfault
I've managed to trap the following segfault with xxgdb and gctorture() set. The segfault seems to move around if gctorture() is not set, but has now occurred twice in the same spot with it set. xxgdb gives the message Program received signal SIGSEGV, Segmentation fault. 0x71244 in RunGenCollect (size_needed=2) at memory.c:1027 and the source listing points to FORWARD_CHILDREN(s); in the