| 1 |
Michael: |
| 2 |
> On Mon, 2021-04-05 at 16:10 +0200, karl@××××××××.se wrote: |
| 3 |
> > system call failed: Cannot allocate memory |
| 4 |
> > Segmentation fault |
| 5 |
> |
| 6 |
> Is this a low-memory machine? |
| 7 |
|
| 8 |
So, how much memory does R need to build ? |
| 9 |
I have: |
| 10 |
|
| 11 |
$ free |
| 12 |
total used free shared buff/cache available |
| 13 |
Mem: 6103628 1807560 2631444 146376 1664624 3107868 |
| 14 |
Swap: 8788924 670108 8118816 |
| 15 |
|
| 16 |
/// |
| 17 |
|
| 18 |
Somewhere in the log it says that something failed to get |
| 19 |
a sigaltstack(). Did the R devs anticipate out of memory and sigseg and |
| 20 |
tried to handle it ? |
| 21 |
|
| 22 |
> If so, there's no much you can do here |
| 23 |
> except set a lower number of jobs in MAKEOPTS for the dev-lang/R build: |
| 24 |
> |
| 25 |
> https://wiki.gentoo.org/wiki//etc/portage/package.env |
| 26 |
|
| 27 |
I already have (in make.conf): |
| 28 |
EMERGE_DEFAULT_OPTS="--jobs 1 ..." |
| 29 |
|
| 30 |
This seems to solved the issue: |
| 31 |
# cat /etc/portage/env/j1 |
| 32 |
MAKEOPTS=-j1 |
| 33 |
# cat /etc/portage/package.env/R |
| 34 |
dev-lang/R j1 |
| 35 |
|
| 36 |
> But if you don't think you're running out of RAM, we can keep digging. |
| 37 |
> For example you might have some memory limits set in /etc/limits that |
| 38 |
> you're hitting. |
| 39 |
|
| 40 |
I don't have an /etc/limits, and /etc/security/limits.conf is just |
| 41 |
comments. |
| 42 |
|
| 43 |
# prlimit -d -l -s |
| 44 |
RESOURCE DESCRIPTION SOFT HARD UNITS |
| 45 |
DATA max data size unlimited unlimited bytes |
| 46 |
MEMLOCK max locked-in-memory address space unlimited unlimited bytes |
| 47 |
STACK max stack size 8388608 unlimited bytes |
| 48 |
|
| 49 |
Regards, |
| 50 |
/Karl Hammar |
Archives