similar to: Creating a long list triggers billions of messages

? Tue, 21 Jan 2025 16:51:34 +1100 Hugh Parsonage <hugh.parsonage at gmail.com> ?????: > x <- vector("list", 2^31) > > which triggers (presumably) billions of error messages like > Error: long vectors are not supported yet ../include/Rinlinedfuns.h I couldn't reproduce this with some released versions of R or a recent R-devel. Would you mind sharing your

I tried doing this on a cloud instance of R 4.4.2 but the terminal exited and the cloud ejected my session shortly after setting the breakpoint and running the program Function "Rf_errorcall" not defined. Make breakpoint pending on future shared library load? (y or [n]) y Breakpoint 2 (Rf_errorcall) pending. (gdb) run Starting program: /opt/R/4.4.2/lib/R/bin/exec/R -q -s -e

On 9/9/20 9:30 AM, Hugh Parsonage wrote: > Thank you! > > I get > > Starting program: C:\R\R-devel-20200909\bin\x64\Rgui.exe > [New Thread 19940.0x638c] > [New Thread 19940.0x102c] > [New Thread 19940.0x329c] > [New Thread 19940.0x37dc] > warning: Invalid parameter passed to C runtime function. > > Program received signal SIGSEGV, Segmentation fault. >

On 9/9/20 8:48 AM, Hugh Parsonage wrote: > I am unable to set break or use gdb with any success when I use that version. > > On linux I would do R -d gdb but this gives "unknown option '-d' " > while gdb R.exe (in the same directory as the debug version) gives the > same output as before. > > I'm happy to help but I appreciate this list might not be the

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

I see that base::pmax() does not support long vectors. Is R-devel interested in reports like this; ie. is there a goal of full support for long vectors in "basic" functions, something I at least would greatly appreciate? MRE: > pmax(rep(1L, 3*10^9), 0) Error in pmax(rep(1L, 3 * 10^9), 0) : long vectors not supported yet: ../../../R-devel-src/src/include/Rinlinedfuns.h:522 Best,

On Tue, Sep 8, 2020 at 11:44 PM Jeroen Ooms <jeroenooms at gmail.com> wrote: > > On Tue, Sep 8, 2020 at 5:20 PM Tomas Kalibera <tomas.kalibera at gmail.com> wrote: > > > > On 9/8/20 4:48 PM, Hugh Parsonage wrote: > > > Unfortunately I only get > > > > > > [Thread 21752.0x4aa8 exited with code 3221225477] > > > [Thread 21752.0x4514

Hi, I am running R 3.3.3 and getting the following error: Error in add_edges(res, edges = t(as.matrix(el[, 1:2])), attr = weight) : long vectors not supported yet: ../../src/include/Rinlinedfuns.h:138 when passing a 13 GB TransitionLayer object to shortestPath from the package 'gdistance'. The error, albeit in a different context, is discussed here:

Kasper, If you're not interested or dont have time to create said patch yourself let me know and i can do it. Best, ~G On Mon, Jan 21, 2019, 11:36 AM Duncan Murdoch <murdoch.duncan at gmail.com wrote: > On 21/01/2019 12:35 p.m., Kasper Daniel Hansen wrote: > > I see that base::pmax() does not support long vectors. > > > > Is R-devel interested in reports like this;

This looks to me like a package development issue... which may be under discussion in R-sig-geo (search the archives), but more likely to be appropriate to discuss with the maintainer by email or through their development repository (R-forge, though it looks unused). -- Sent from my phone. Please excuse my brevity. On February 14, 2018 7:43:51 AM PST, Loris Bennett <loris.bennett at

On Tue, 8 Sep 2020, Hugh Parsonage wrote: > Thanks Martin. On further testing, it seems that the segmentation > fault can only occur when the amount of obtainable memory is > sufficiently high. On my machine (admittedly with other processes > running): > > $ R --vanilla --max-mem-size=30G -e "x <- c(0L, -2e9:2e9)" > Segmentation fault > > $ R --vanilla

I think that this is because `[<-` dispatches on S4 methods only if the first argument is S4. ?"[<-" says: "These operators are also implicit S4 generics, but as primitives, S4 methods will be dispatched only on S4 objects ?x?." Georgi Boshnakov -----Original Message----- Message: 19 Date: Tue, 8 Sep 2020 22:04:44 -0400 From: Ben Bolker <bbolker at

On 9/8/20 4:48 PM, Hugh Parsonage wrote: > Unfortunately I only get > > [Thread 21752.0x4aa8 exited with code 3221225477] > [Thread 21752.0x4514 exited with code 3221225477] > [Thread 21752.0x3f10 exited with code 3221225477] > [Inferior 1 (process 21752) exited with code 030000000005] > > (I'm guessing I would need to build an instrumented version of R, or > can R

Thanks for the quick responses. As you both suggested storing the packages to local drive is feasible but comes with a size restriction I wanted to avoid. I'll keep this in mind as plan B. @Hugh: 2. would impose even greater slowdowns and 4. is just not feasible. However, 3. sounds interesting - how would this work in a Linux environment? Thank you, Mario Am So., 19. Juli 2020 um 20:11 Uhr

Hi Jeff, Jeff Newmiller <jdnewmil at dcn.davis.ca.us> writes: >> Hi, >> >> I am running R 3.3.3 and getting the following error: >> >> Error in add_edges(res, edges = t(as.matrix(el[, 1:2])), attr = weight) >> : >> long vectors not supported yet: ../../src/include/Rinlinedfuns.h:138 >> >> when passing a 13 GB TransitionLayer

Lines 129-131: \code{grep(value = FALSE)} returns a vector of the indices of the elements of \code{x} that yielded a match (or not, for \code{invert = TRUE}. This will be an integer vector unless the input There should be a closing parenthesis after \code{invert = TRUE}

| Confirmed for R-devel (current) on Ubuntu 17.10. But ... isn't the regexp | you use wrong, ie isn't R-devel giving the correct answer? No, I don't think R-devel is correct (or at least consistent with the documentation). My interpretation of gsub("(\\w)", "\\U\\1", entry, perl = TRUE) is "Take every word character and replace it with itself, converted to

Hello, After some fuzz testing I found a problem with Rf_isVector() function in R 3.5.0. Platform: Ubuntu 16.04 Compiler: Clang-4.0 (from Ubuntu's repository) + ASAN Crashing R code:

>>>>> Martin Maechler >>>>> on Tue, 8 Sep 2020 10:40:24 +0200 writes: >>>>> Hugh Parsonage >>>>> on Tue, 8 Sep 2020 18:08:11 +1000 writes: >> I can only reproduce on Windows, but reliably (both 4.0.0 and 4.0.2): >> $> R --vanilla >> x <- c(0L, -2e9:2e9) >> # > Segmentation

I propose a patch to ifelse that leverages anyNA(test) to achieve an improvement in performance. For a test vector of length 10, the change nearly halves the time taken and for a test of length 1 million, there is a tenfold increase in speed. Even for small vectors, the distributions of timings between the old and the proposed ifelse do not intersect. The patch does not intend to change the