Re: [racket-users] [FFI] malloc, maximum number of bytes

Okay, got to the bottom of it. racket-mode uses racket-memory-limit that is set to 2048 by default. Setting it to 0 makes it unlimited. On Sunday, July 28, 2019 at 8:19:11 PM UTC+2, Matthew Flatt wrote: > > Ah, it's possible that Racket mode sets a limit on Racket's memory use, > just like DrRac

Re: [racket-users] [FFI] malloc, maximum number of bytes

Ah, it's possible that Racket mode sets a limit on Racket's memory use, just like DrRacket does. That kind of memory limit (enforced within Racket, instead of by the OS) is based on GCable memory, so it doesn't limit 'raw allocation. At Sun, 28 Jul 2019 11:12:04 -0700 (PDT), Peter Samarin wrote: >

Re: [racket-users] [FFI] malloc, maximum number of bytes

I just rerun the example on the commandline and it works just fine with larger numbers of bytes. I use emacs and racket-mode by Greg Hendershot. I will check how that starts racket at some other time. Thanks Matthew! On Sunday, July 28, 2019 at 8:06:09 PM UTC+2, Matthew Flatt wrote: > > There sh

Re: [racket-users] [FFI] malloc, maximum number of bytes

There should be no special limit on 'atomic memory, and I haven't been able to replicate this behavior, yet. Can you say more about how you're running (e.g., in DrRacket versus command-line `racket`)? Also, although it's difficult to see how it could matter, which Linux distribution do you use? A

[racket-users] [FFI] malloc, maximum number of bytes

Hi all, I am using Racket v7.3, Linux x86_64 version. I want to allocate large (tens of gigabytes) chunks of memory with Racket's malloc and use them for some BLAS/LAPACK routines. The downloaded version of Racket lets me allocate only 2^31 "atomic" bytes. 2^31+1 bytes produce an "out of memory"