Occasional Crash
Comments
-
bump for attention 4
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
The crashes are still not reproducible but happen more frequently than usual. Here is another log:
https://www.dropbox.com/s/p70idqqscqmy5ea/LogosLogs.20211226-071520.zip?dl=0
0 -
Any suggestions from people who understand the logs?
0 -
Armin said:
Any suggestions from people who understand the logs?
Curious about network stability ? Logos.log file has many Logos Sync Client errors, including one preceding crash.
Keep Smiling [:)]
0 -
Curious about network stability ? Logos.log file has many Logos Sync Client errors, including one preceding crash.
Keep Smiling
I agree that there seems to be a link to the network and syncing. While I had a unreliable and slow internet connection in the past, I now have fairly fast and reliable internet. However, I notice that when many panels are open, the sync icon occasionally displays a "!". In these situations, closing all panels can lead to a crash.
Some years ago (maybe 3 years?), this problem was even worse but then the syncing was redesigned. While there is a significant improvement since then, I occasionally still get the crashes.
0 -
Here is another log after a crash:
https://www.dropbox.com/s/m60h9oi8jmf7yzv/LogosLogs.20220106-055411.zip?dl=0
0 -
Armin said:
Here is another log after a crash:
https://www.dropbox.com/s/m60h9oi8jmf7yzv/LogosLogs.20220106-055411.zip?dl=0
Do you have any idea how many panels you had opened? Was this a layout? A screenshot or video would help in trying to reproduce.
0 -
Yes, this was a layout. I tend to have 2-3 Logos windows open with several panels and resources. Some resources are linked. I include a screenshot of the main window below.
A while back, I started the practice to first close all Logos windows and then shut down the software. At startup, I first start Logos without any resources open, then load a layout. This has reduced the number of hiccups. But I still get the occasional crash.
A recent upgrade of my Internet connection (~100Mbps download and ~20Mbps upload) did not help.
0 -
Here is another log after a crash that occurred when trying to close all tabs using the icon in the top right corner of the main Logos window. At the time of the crash, 3 Logos windows were open.
0 -
Armin said:
Yes, this was a layout. I tend to have 2-3 Logos windows open with several panels and resources. Some resources are linked. I include a screenshot of the main window below.
A while back, I started the practice to first close all Logos windows and then shut down the software. At startup, I first start Logos without any resources open, then load a layout. This has reduced the number of hiccups. But I still get the occasional crash.
A recent upgrade of my Internet connection (~100Mbps download and ~20Mbps upload) did not help.
Armin,
Is this only one window? Or do you have multiple floating windows? I'm trying to clarify what you mean by windows since you only have one screenshot with multiple panels shown.
0 -
Philana R. Crouch said:
Armin,
Is this only one window? Or do you have multiple floating windows? I'm trying to clarify what you mean by windows since you only have one screenshot with multiple panels shown.
I typically have the Logos main window and one or two floating windows, each with multiple resources open.
0 -
Armin said:
I typically have the Logos main window and one or two floating windows, each with multiple resources open.
It may be helpful to provide screenshots of the floating windows as well when the crash happens next time.
“The trouble is that everyone talks about reforming others and no one thinks about reforming himself.” St. Peter of Alcántara
0 -
SineNomine said:
It may be helpful to provide screenshots of the floating windows as well when the crash happens next time.
I experience crashes (not hangs), i.e., Logos just disappears off the screen. I therefore cannot make a screenshot anymore.
0 -
I continue to suspect that the crashes are somehow linked to the communication between my Logos app and the FL Servers.
Here is an examples of the networking issues, which, however, this time did not result in a crash:
When running Logos with my 3 floating windows and with numerous resources open, the sync icon displayed the tool tip that there are unsynced items. When I clicked on the circle, it tried to sync. When the sync icon stopped circulating, it again stated that there are unsynced items. After clicking the sync icon a few times, I got the exclamation mark in the sync icon and the tooltip that an error occurred while syncing. Several clicks on the sync icon did not resolve the error. The exclamation mark remained.
When I then closed all windows and resources, clicked on the sync icon, it all worked and the sync finished.
I suspect that in the case of a complex layout, the communication between Logos and FL servers has problems.
0 -
Armin said:
When the sync icon stopped circulating, it again stated that there are unsynced items. After clicking the sync icon a few times, I got the exclamation mark in the sync icon and the tooltip that an error occurred while syncing. Several clicks on the sync icon did not resolve the error. The exclamation mark remained.
Reproduce this with logging enabled and upload the compressed zip file using the paper-clip icon.
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
Reproduce this with logging enabled and upload the compressed zip file using the paper-clip icon.
Logging was enabled at that time. I believe it happened on Jan 23 around 6am.
0 -
Just now, it happened again. In this case, I noticed the problem when a Logos video did not play back anymore. So the "!" in the sync icon appeared. However, closing the layout (incl. all windows and resources) did not fix it. I then loaded a very simple layout. Then the sync recovered.
0 -
Here is another log of a crash when closing a complex layout:
0 -
Let's get rid of a few other errors that are occurring: Delete these folders:
- CloudResourceManager
- UpdateManager
- DownloadManager
at /Users/eberlein/Library/Application Support/Logos4/Data/ql9dcp7b.59i
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
Let's get rid of a few other errors that are occurring: Delete these folders:
- CloudResourceManager
- UpdateManager
- DownloadManager
at /Users/eberlein/Library/Application Support/Logos4/Data/ql9dcp7b.59i
Many thanks, Dave. I deleted them and will post logs should Logos crash again.
0 -
Armin said:Dave Hooton said:
Let's get rid of a few other errors that are occurring: Delete these folders:
- CloudResourceManager
- UpdateManager
- DownloadManager
at /Users/eberlein/Library/Application Support/Logos4/Data/ql9dcp7b.59i
Many thanks, Dave. I deleted them and will post logs should Logos crash again.
Hi Dave,
Many thanks. So far, I haven't had a crash. It looks like it might have fixed the issue.
0 -
If you don't mind uploading another set of logs with a Close All, I can compare them with the last set
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
If you don't mind uploading another set of logs with a Close All, I can compare them with the last set
Sorry for the delay.
I just installed the newest beta. And it just happened again that a Close All again caused a crash. Here are the logs: 3173.LogosLogs.20220209-083008.zip
0 -
Armin said:Dave Hooton said:
If you don't mind uploading another set of logs with a Close All, I can compare them with the last set
Sorry for the delay.
I just installed the newest beta. And it just happened again that a Close All again caused a crash. Here are the logs: 3173.LogosLogs.20220209-083008.zip
Hi Armin,
I forgot to reply back to you. We do have an open case, but it has been challenging to consistently reproduce the crash.
0 -
Philana Crouch said:
Hi Armin,
I forgot to reply back to you. We do have an open case, but it has been challenging to consistently reproduce the crash.
Hi Philana,
Thanks for following up. Yes, it does not happen on a regular basis. Although I have tried it, I cannot determine a reliable way to reproduce the crash.
0 -
Here are 3 more logs of crashes after close all:
4505.LogosLogs.CloseAllCrash.20220216-053102.zip
0 -
Here is another log with a crash after "close all":
0 -
Also 9.12 has not yet fixed this crash:
0 -
Yes, it is fixed! Many thanks.
0
said:
