You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The global threadpool does keep idle threads around, by design. If you create your own ThreadPool, you can exert more control -- we don't have a synchronous shutdown (#688), but they will exit "soon" after the ThreadPool drops.
can the threadpool be closed manually with the default threadpool? because i had noticed that there are some extra threads where i wouldnt expect them to still be around GuillaumeGomez/sysinfo#927
because it is only used once per command start (and only if command is "download")
which will leave rayon global threads hanging around which are never used again
(and the global thread pool cannot be closed)
see rayon-rs/rayon#959
Can you check/confirm that this bug has to do with Rayon? https://gitlab.gnome.org/GNOME/librsvg/-/issues/865
Thanks.
The text was updated successfully, but these errors were encountered: