MATLAB parallel pool startup takes forever when setting a network path as current folder

4 views (last 30 days)
yunhui zhou
yunhui zhou on 22 Dec 2019
Edited: yunhui zhou on 22 Dec 2019
Hello, I am using MATLAB R2019a (update 2 or 3) and R2018b (Update 5) currently. I find that when using MATLAB on Windows 10 and setting a windows shared folder on the network as current folder, starting the parallel pool usually (I would say 70% for R2019a, 20% for R2018b) takes forever (at least more than 120 min). No error message, zero CPU consumption, and the memory occupied by each individual MATLAB worker usually gets stucked at 290-310 MB. It happens in many different computers and laptops in my lab. Pressing "Ctrl+C" to abort the startup process and restart the parallel pool does not help. I hope to know the reason and solution for this phenomenon.
Pressing Ctrl+C during the startup process gives the following error output:
at com.mathworks.mvm.exec.FutureResult.getInternal(
at com.mathworks.mvm.exec.FutureFevalResult.getInternal(
at com.mathworks.mvm.exec.FutureResult.get(
at com.mathworks.toolbox.distcomp.util.mvm.Async$1.done(
at com.mathworks.mvm.exec.MvmSwingWorker$1$
at java.awt.event.InvocationEvent.dispatch(
at java.awt.EventQueue.dispatchEventImpl(
at java.awt.EventQueue.access$500(
at java.awt.EventQueue$
at java.awt.EventQueue$
at Method)
at java.awt.EventQueue.dispatchEvent(
at java.awt.EventDispatchThread.pumpOneEventForFilters(
at java.awt.EventDispatchThread.pumpEventsForFilter(
at java.awt.EventDispatchThread.pumpEventsForHierarchy(
at java.awt.EventDispatchThread.pumpEvents(
at java.awt.EventDispatchThread.pumpEvents(

Answers (0)

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!