Closed Yunuuuu closed 1 year ago
Hello. It's clear that something causes the parallel workers to completely crash, regardless of you running 'multicore' or 'multisession' workers. Since it happens to both backends, it's likely to be independent of the parallel backend. If you tried with plan(future.callr::callr)
, you'd probably see the same there.
Depending on your Linux setup, it could be that you're running out of memory, and Linux decides to terminate your workers. If you've seen some error from Linux like "Out of Memory (OOM) killer", then that's the reason.
Regardless, I'd suggest that you try with fewer workers to see if you can reproduce the crash. Try with workers = 2
, or even a single one, which you can get by workers = I(1)
[note the I()
]. If that works for you, try to increase the number of workers until you experience the problem. Pay attention to the system's memory usage, e.g. look at top
or htop
.
If it still crashes with workers = I(1)
, then see if it even workers when running sequentially, i.e. plan(sequential)
. It could be that it crashes then too. You could even check that cases the first thing you do.
(Please use https://github.com/HenrikBengtsson/future/discussions for Q&A) Hi, thanks for your great R package future which really convenient to run long-long task.
Describe the bug
A clear and concise description of what the bug is.
I begin to run this function with
future::plan("multicore", workers = 10L)
, it also gave similar error infos as belows, so I tried above multisession as indicated in https://github.com/HenrikBengtsson/future/issues/474the
rrho_correct_pval
is a long function deposited in https://github.com/Yunuuuu/biomisc/blob/81948d2e5e2bab5a4cf76fd76e8ab4a096192efd/R/run_rrho.R#L787I put the main future function here:
Reproduce example
Actually, the biomisc::run_rrho also use future_lapply but it won't often gave a error (it'll also gave error randomly, I cannot reproduce biomisc::run_rrho error message, but I run biomsc::rrho_correct_pval after biomisc::run_rrho which will often reproduce above error (use my own data: gene expression array data)).
But when I use a artificial data (I cannot make error occur, so I can't give reboust example code to reproduce this error)
Expected behavior
Run without error
Session information
Please share your session information after the error has occurred so that we also see which packages and versions are involved;