Check process probably crashed or hung up for 20 minutes ... killed
Most likely this happened in the example checks (?),
if not, ignore the following last lines of example output:
  object '.slaveRSOCK' not found
Calls: ::: -> get
Execution halted
Warning in doTryCatch(return(expr), name, parentenv, handler) :
  NAs introduced by coercion
Warning in doTryCatch(return(expr), name, parentenv, handler) :
  NAs introduced by coercion
Warning in doTryCatch(return(expr), name, parentenv, handler) :
  NAs introduced by coercion
Warning in doTryCatch(return(expr), name, parentenv, handler) :
  NAs introduced by coercion
Warning in doTryCatch(return(expr), name, parentenv, handler) :
  NAs introduced by coercion
Warning in doTryCatch(return(expr), name, parentenv, handler) :
  NAs introduced by coercion
Warning in doTryCatch(return(expr), name, parentenv, handler) :
  NAs introduced by coercion
Error in socketConnection("localhost", port = port, server = TRUE, blocking = TRUE,  : 
  Failed to launch and connect to R worker on local machine 'localhost' from local machine 'CRANWIN'.
 * The error produced by socketConnection() was: 'cannot open the connection'
 * In addition, socketConnection() produced 1 warning(s):
   - Warning #1: 'port 37400 cannot be opened' (which suggests that this port is either already occupied by another process or blocked by the firewall on your local machine)
 * The localhost socket connection that failed to connect to the R worker used port 37400 using a communication timeout of 120 seconds and a connection timeout of 120 seconds.
 * Worker launch call: "D:/RCompile/recent/R/bin/x64/Rscript" --default-packages=datasets,utils,grDevices,graphics,stats,methods -e "#label=future-Ex.R:185496:CRANWIN:CRAN" -e "try(suppressWarnings(cat(Sys.getpid(),file=\"D:/temp/RtmpAna9s7/future.parent=185496.2d498366511b9.pid\")), silent = TRUE)" -e "parallel:::.slaveRSOCK()" MASTER=localhost PORT=37400 OUT=/dev/null TIMEOUT=120 XDR=TRUE.
 * Worker (PID 82748) was successfully killed: TRUE
 * Troubleshooting suggestions:
   - Suggestion #1: Set 'verbose=TRUE' to see more details.
   - Suggestion #2: On Windows, output from worker when using 'outfile=NULL' is only visible when running R from a terminal (not a GUI).
Calls: plan ... tryCatchList -> tryCatchOne -> <Anonymous> -> <Anonymous>
Execution halted
======== End of example output (where/before crash/hang up occured ?) ========