Replies: 1 comment
-
This and the rest of the "breadcrumbs" in the error message and your session information strongly suggest that you're running out of memory. I don't know CellChat well enough, but it looks like it's hardcoding use of multisession internally and defaulting to Either way, this is a question for CellChat, so please bring this up at https://github.com/jinworks/CellChat/issues |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the bug
When I run
Warning: Caught FutureLaunchError. Canceling all iterations ...
Error: Caught an unexpected error of class FutureError when trying to launch future (‘future_sapply-9’) on backend of class MultisessionFutureBackend. The reason was: MultisessionFuture (‘future_sapply-9’) failed to launch future on cluster RichSOCKnode #9 (PID 42096 on localhost ‘localhost’). The reason reported was ‘error writing to connection’. Post-mortem diagnostic: No process exists with this PID, i.e. the localhost worker is no longer alive. The total size of the 11 globals exported is 27.14 GiB The three largest globals are ‘...future.FUN’ (11.18 GiB of class ‘function’), ‘FunMean’ (11.18 GiB of class ‘function’) and ‘data.use’ (4.58 GiB of class ‘numeric’)
In addition: Warning message:
In asMethod(object) :
sparse->dense coercion: allocating vector of size 4.6 GiB
It raises error when running into
computeExpr_LRfunction. Here is the detailed function.Session information
Please share your session information after the error has occurred so that we also see which packages and versions are involved;
Beta Was this translation helpful? Give feedback.
All reactions