Slicer program closes after logging out and back in on Windows 10


I’ve noticed a recurring problem I have with my installation of Slicer 4.112021226. The problem is this:
when I have the program open, then log out (with program still open) of my profile on the machine, then log back in, the program window closes spontaneously after a few seconds. What happens is the red X button in the top right corner looks like it has been pressed (it hasn’t), then the main header bar reads (Not Responding), then crash.

The OS I’m using is Windows 10 Pro. I wondered if it might be a graphics issue, but there are no problems like this when I’m actively running the program, even for heavy tasks. Uninstalling and re-installing the same version (latest stable one – 4.112021226) doesn’t solve the problem.

Any advice/help/insight is so appreciated, thank you!!

When you log out (more accurately “Sign out”) from Windows10 then all the applications will be closed, so Slicer (and none of the other applications) will resume when you sign in again. What do you mean exactly by “log out”: sign out, lock the computer (hit Windows+L), put the computer into sleep, hibernate the computer, switch users, …?

I could not reproduce a Slicer crash on my computer with any of the above “log out” operations but if you have multiple monitors, older computer, not very robust drivers, etc. then locking your computer or putting into sleep might provoke an application error.

To be honest, I’m not 100% sure what occurs on this “log out” that I describe, because this problem happens (as far as I know) only when I’m accessing the PC with Slicer on it remotely via Windows Remote Desktop. Specifically, what happens (sometimes) is that my remote connection is disrupted, so I have to “log in” again to the PC (i.e. reestablish the remote connection), and that’s when I encounter this problem. That said, I think by “log out” I mean a simple lock operation, since when this happens none of the other programs closes or is disrupted in any way.

Perhaps what you mention about the multiple monitors issue could be at work here? Or maybe it’s a driver issue?

Thanks for trying to reproduce the errors! Sorry I wasn’t clearer before.

Maybe what I’ll have to do is run Slicer locally rather than remotely…

Thanks for the information, it is very useful. Remote desktop connection is an entirely different story than working locally. Slicer relies on hardware-accelerated graphics and Windows Remote Desktop Protocol earlier did not support this at all. Recent years Windows versions allow remotely started applications to access graphics hardware, but apparently it is not robust.

Updating tour graphics drivers might solve the issue (or the issue may get fixed by future Windows or graphics driver updates).

If updates don’t help then I would recommend to use a different remote desktop client, such as RealVNC, AnyDesk, Chrome Remote Desktop, NoMachine, or TightVNC. They all work at a bit higher level than Windows RDP (grab the rendered screen content) therefore they are much more robust.

If you must use Windows RDP then you can switch to a software renderer. This
will make the application not use hardware acceleration anymore, so it should be less sensitive to graphics driver bugs, but it makes rendering slower.

This is extraordinarily helpful! Thanks so much for this detailed explanation and feedback. These sorts of software details are things I don’t think about reflexively because I don’t have so much expertise there.

I (quite naively, I guess!) didn’t even know there were other options for the remote desktop. I’ll be sure to try out one/some and report back!

Thanks again!

1 Like

I just tried setting up a connection using NoMachine, and it appears to solve the problem! I didn’t really stress test it too much yet, but it looks promising.

Either way, I will have discovered a new, more robust remote desktop software that I like a lot better than Windows Remote Desktop!

Thanks so much again!!

1 Like