Extension manager hangs and crashes Slicer 5.10 today

Support
1

I am using Slicer 5.10 on Windows, and wanted to add the model to model distance extension today. However, when I open the Extension Manager, I get a blank window and spinning waiting cursor for an indefinite period, apparently hanging. If I try to close the window, Windows asks if I want to close end the process because it is not responding, and if I do that, it closes Slicer as well. I don’t know if this could be related to Release of Slicer 5.12 in progress ? In any case, it is disruptive to not be able to try to access the extension manager in a prior stable release, and if I had not saved my work prior to trying to open the extension manager, I would have lost that work as well since there was no way to close the extension manager window without force-closing Slicer. I have used the extension manager many times in the past, including with my current Slicer installation and network configuration without problems, so that is why I suspect it is something on the remote end which could be the issue. Is anyone else running into this problem? Is it known that the extension manager is down temporarily due to the 5.12 release? Thanks for any insight you can provide.

2

The extension manager works the same way as before and there is no difference in how it displays extensions for various Slicer versions. Due to the extension builds for Slicer-5.12 were completed and uploaded to the extension server during the day, it is possible that the server was slower, but it should have recovered over time (or timed out). Maybe stopping network connections (e.g., by unplugging the network cable or turning off WiFi for a few seconds) could have forced the page loading to fail faster and allow you to close the browser faster. Let us know if the issue comes up again.

3

Thanks for the response. I will check again tomorrow and try resetting my network connections.

4

Turning off wifi and reconnecting did not trigger a timeout or error message, but restarting my laptop did resolve the issue today. Thanks much for the notification that this wasn’t a general issue, @lassoan.