Comments (2)
I don't have much knowledge in this area, but one thing you could try, both to narrow in on the root issue of the crash and as an alternative to "multisession" is to install the package "future.callr" and then use the following plan (instead of the "multisession" plan):
future::plan(future.callr::callr)
If you don't switch back to sequential at the end, do things still work well with the above plan?
from future.
@scottkosty
Yes, using future.callr::callr
as plan works as intended. R processes are spammed when computation begins, and closed afterwards, freeing the memory. Also, Rstudio doesn't crash when restarting/closing session without changing plan to sequential.
I can use this workaround for the moment for my own development, but I would like to know why is this happening with plans from future
, as is the default recommendation in docs from furrr
and other packages and probably the one that users of the package I'm developing will use.
Is there any more info I can provide to help narrowing the issue?
from future.
Related Issues (20)
- Incremental async reduction HOT 5
- deleted/invalid
- Error in unserialize(node$con) : MultisessionFuture (future_lapply-4) failed to receive results from cluster RichSOCKnode #4 (PID 436932 on localhost ‘localhost’). The reason reported was ‘error reading from connection’. Post-mortem diagnostic: No process exists with this PID, i.e. the localhost worker is no longer alive. HOT 1
- Issues with foreach and SGE HOT 3
- global r6 instances are modified and unusable in multisession HOT 7
- namespace:future'没有出口‘multiprocess’这个对象 HOT 1
- plan(cluster) over ssh asks for port to be specified in workRSOCK() HOT 2
- future() and resolved() handle FutureError:s differently for different backends
- R CMD check NOTE: Documented arguments not in \usage in documentation ...
- ‘error reading from connection’. Post-mortem diagnostic: No process exists with this PID, i.e. the localhost worker is no longer alive. HOT 2
- detritus NOTE when multisession plan declared in vignette HOT 1
- Some R packages change 'future.*' options permanently
- Nested Futures Use More Memory Than They Should HOT 1
- Detect a future parallel backend HOT 1
- plan(cluster, workers = <cluster>) has more overhead than plan(cluster, workers = <integer>) HOT 6
- Add `arrow` to the list of packages with non-exportable objects? HOT 5
- `future_lapply` ran into `subscript out of bounds` error when function have use `$<-` with magrittr pipe. HOT 4
- Backend hook function for shutting down/cleaning up backend HOT 1
- Error: ‘inherits(future, "Future")’ is not TRUE HOT 18
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from future.