Skip to content
Prev 8493 / 21312 Next

[Bioc-devel] bplapply Processes Sometimes Stall

Hi Dario -- the most likely explanation, without a reproducible example, is that the code used on workers sometimes puts R into a state that it cannot recover from.

The first approach to debug this is to run the code serially, e.g., using SerialParam and perhaps register(SerialParam()) (to make serial evaluation the default in a bplapply() invoked without a BPPARAM argument).

BiocParallel 1.5.12 is from the 'devel' branch of Bioconductor, which is supposed to be used (currently) on R-devel; please always use the appropriate version of R, with packages installed using biocLIte() when reporting problems.

Probably this belongs on support.bioconductor.org, where others may more easily benefit from your experience.

There are a couple of things that have come up while looking in to your problem and how R can get into the situation where several processes share a socket connection in the CLOSE_WAIT state; I'm still exploring solutions but it is not obvious that these would address whatever your underlying issue might be; R might be more helpful in saying that something has gone wrong, without being able to say exactly what.

Martin