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
On a clean install on Windows, sometimes the Loading dialog does not appear and the user sees only a maximized completely white screen other than the Windows menu bar.
#7115
Open
cckozie opened this issue
Oct 13, 2020
· 2 comments
3.0.1 (343c98b)
I've first experienced this in this build. The screen was totally empty other than the Windows menu bar for about 2 minutes (on my quad core i7 machine) before the Get Started screen came up. Rich Mann also experienced this when testing the PR. I have not been able to replicate it.
The text was updated successfully, but these errors were encountered:
I did see this again when testing another issue. (#7116) I think they may be related. It looks like at some point during the initial opening of tC it starts another instance of it. Sometimes the screen from that second instance is displayed instead of the Loading one.
Looks like this problem also existed in 3.0, and maybe earlier.
When testing with 3.0 I noticed that when choosing the Close tC option on the Git is Required dialog, even though the tC icon in the taskbar disappears, there are still 4 tC tasks running when looking in the Background Processes of the Task Manager. The second tC instance is then started near the end of the loading process.
We should add to the Installation section of the release notes that when doing an install and including the Git installation:
The user may see a completely white screen for several minutes before the Welcome to translationCore screen is displayed.
When the installation completes and the user sees the Welcome to translationCore screen, they should right click on the tC icon in the task bar and choose the "Close all windows" option, then start tC again.
3.0.1 (343c98b)
I've first experienced this in this build. The screen was totally empty other than the Windows menu bar for about 2 minutes (on my quad core i7 machine) before the Get Started screen came up. Rich Mann also experienced this when testing the PR. I have not been able to replicate it.
The text was updated successfully, but these errors were encountered: