In addition you can also try to use a PSOCK cluster (see makeCluster,
parLapply) to avoid the problem - it should help if the problem is
somehow related to forking in mclapply().
The problem you are seeing may be in base R, in data.table, or in
interaction between the two (mclapply() from
On 4 April 2019 at 17:28, ivo welch wrote:
| The following program is whittled down from a much larger program that
| always works on Intel, and always works on AMD's threadripper with
| lapply but not mclappy. With mclapply on AMD, all processes go into
| "suspend" mode and the program then
The following program is whittled down from a much larger program that
always works on Intel, and always works on AMD's threadripper with
lapply but not mclappy. With mclapply on AMD, all processes go into
"suspend" mode and the program then hangs. This bug is replicable on an
AMD Ryzen
