-
Notifications
You must be signed in to change notification settings - Fork 2
Description
I saw this issue in one of my Shiny logs, and found similar ones here: satijalab/seurat#1845
But I am not using the seurat package, but the AsyncProgress function from ipc.
Loading required package: shiny
Listening on http://0.0.0.0:9999
Unhandled promise error: ungültiger Argumenttyp
Warnung: Error in getGlobalsAndPackages: The total size of the 10 globals exported for future expression (...
This exceeds the maximum allowed size of 500.00 MiB (option 'future.globals.maxSize'). The three largest globals are ‘progress’ (507.65 MiB of class ‘environment’), ‘dbConnect’ (27.67 KiB of class ‘function’) and ‘svd_changes’ (8.24 KiB of class ‘list’)
This R snippet trigered that error, but I was mainly wondering why the progress object should be around 507 MiB..
progress = AsyncProgress$new(message="Changes saved")
myFuture <- future(seed = NULL, label = "SaveToDatabase", {
con_fut <- dbConnect(...)
on.exit(dbDisconnect(con_fut), add = TRUE)
progress$inc(0.1, message = "Connected")
handle_svd_changes(con_fut, svd_changes, name, config, tblname, progress)
})
then(
myFuture,
onFulfilled = function(value) {
progress$close()
},
onRejected = function(reason) {
progress$close()
}
)
I am using this option now as commented n the other issue:
options(future.globals.maxSize = 8000 * 1024^2)
We'll see if it reappears..