Crash Opening (Logo just hung on screen)
I had closed B4. Then a little while later i tried to open it again (i always use the Ctrl key). The L4 logo showed, but it never opened. i open the task manager after a couple of minutes, it showed that L4 was running OK. So i eventually used task manager to shut it down. (very strange seeing just the L4 logo on the middle of the desktop, never saw the sign-in screen).
Edit: tried to do this again, same results. In task manager under applications, it showed one one instance of L4 running. But i looked in task manager under processes showed 3 instances of Logos4.exe running (this means that the original instance did not close properly, the original one i had shut done several minutes earlier). So i started closing down each instance in the processes, after shutting down the 2nd of 3, L4 opened (the 3rd instance in the processes).
Don't know if this helps???
Comments
-
Not seen this before with L4 (have seen it with FireFox many times).
What OS are you using?
Did you have an L4 crash at any time prior to the time you couldn't restart it?
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
Steve,
I had this happen before, but I couldn't reproduce it. I think Logos was doing some major syncing in the background when I shut it down once, and it hung (not visibly, but the process was still in the task manager). Then when I tried to start it again, I had the conditions you describe.
I've complained about sync issues in the past, because it seems like the syncing routines aren't robust enough or efficient enough. But I haven't had the problem in a while, so I can't say for sure that's what caused it.
MacBook Pro (2019), ThinkPad E540
0 -
Richard DeRuiter said:
What OS are you using?
Did you have an L4 crash at any time prior to the time you couldn't restart it?
using Vista home premium (32 bit)
i had no crashes, it had been open for a while, i had hibernated a couple of times. But it was running for a few hours after the last hibernate with no problems.
Since the problem, i have had no other problems.
thanks
0 -
Todd Phillips said:
I had this happen before, but I couldn't reproduce it. I think Logos was doing some major syncing in the background when I shut it down once, and it hung (not visibly, but the process was still in the task manager). Then when I tried to start it again, I had the conditions you describe.
Sounds very much like my problem. i run logging everytime, and i will keep an eye on the task manager and syncing for a while to see if it happens again.
thanks
0 -
steve clark said:
using Vista home premium (32 bit)
Okay. Just wanted to know in case this comes up again for someone else. (Failure to unload a program could be an OS issue - though it's usually a program error.)
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
Richard DeRuiter said:steve clark said:
using Vista home premium (32 bit)
Okay. Just wanted to know in case this comes up again for someone else. (Failure to unload a program could be an OS issue - though it's usually a program error.)
Hmm. I'm running XP SP3. FWIW.
MacBook Pro (2019), ThinkPad E540
0
