FreeShow sometimes fails to start up properly

[yurividal]

I've been experiencing this issue since quite a few versions back, and it is still present in 1.5.5

Windows 11. My data location is set to the default (user\Documents\FreeShow)

Sometimes, when we open FreeShow, it feels a bit slow, and when this happens, we are unable to load any shows, or scriptures. It just spins forever, on the project list panel, and on the main panel.
The sollution is to kill freeshow from the task manager, and re-launch it

Error log json doesn't show any errors, and I still haven't been able to identify exactly what needs to happen for the issue to appear. It seems pretty random to me.

I've seen at least one user rerport this of facebook too.

What can i do to try to troubleshoot this? Is this a known issue?

[vassbo]

Can you try to recreate this with the console to see if there's any errors there? I have not encountered this myself.

[yurividal]

Yeah, I don't think I've ever been able to reproduce it on my dev machine.
But it happens quite often on the church computer. I don't have the console environment setup over there.

[vassbo]

Installing as administrator might help if it's a permission issue.

[vassbo]

You can try running from the command line as well sometime and let me know if there's any errors there.

[Michael-MRC]

This sounds exactly the same as the issue I have, where it just spins for an extremely long period of time. I always end up force quitting and opening again. This happens the first launch of FreeShow every day it's used.

I also haven't been able to reproduce it at home, on a virtually identical build machine.

[vassbo]

Thanks. I would like to fix this, but it's hard to recreate.

[vassbo]

Can this be related to auto backup or any cloud syncing or planning center fetching?

[yurividal]

I don't have any cloud features enabled

[vassbo]

What about the auto backup?

[yurividal]

Yes, I have weekly auto backup enabled.

[vassbo]

Do you think it can be related to that or not?

[yurividal]

Hum.... This would make sense, and probably explain why it only seems to happen once in a while. Perhaps once a week...
I'll try to enable daily backups on my test computer, and see how it behaves for a few days

[vassbo]

I just fixed a few issues where it tried to load too many and too large files into memory, so it might as well be fixed on the dev branch, not sure. (Or it might have the fix on the cloud branch only atm)