[BUG] Logos 7 crashes if network connection changes

Here is the scenario: I start up Logos 7 with a network connection. While using L7, the network disconnects (e.g., wireless goes down, VPN disconnects,...). L7 then hangs and cannot be shut down any more. The CPU goes really high. The only way out is to force quit L7.

I use L7 on a Mac.

Armin

Find more posts tagged with

Comments

Dave Hooton

It would help to post logs (simulate network disconnection if necessary)

Armin

https://community.logos.com/discussion/comment/856610#Comment_856610

Here are the steps that I performed:

- Connected VPN

- Started Logos

- Disconnected VPN

- Tried to close Logos

- Logos hangs (although this time the CPU did not go up)

- I took a sample and filed the logs

Uploading the logs to the forum did not work. So here is a link to the file on Dropbox:

https://www.dropbox.com/s/i8cmndiz8bv75sz/LogosLogs.20161006-195102.zip?dl=0

Dave Hooton

https://community.logos.com/discussion/comment/856770#Comment_856770

The logos.log shows you have a number of long collection rules which take over 50s to evaluate. Many are duplicates, some differ in one name. Look to simplifying or deleting some collections. I'm not sure about their contribution to the hang but it would benefit startup time and program response.

Armin

https://community.logos.com/discussion/comment/856851#Comment_856851

Hi Dave,

I agree that the crash is not related to collection rules as it is clear that the crash only happens when the network connection changes.

But thanks for pointing out that complex collection rules can slow down startup. I will delete some of the collections that I don't use.

Armin

Philana R. Crouch

Here is the scenario: I start up Logos 7 with a network connection. While using L7, the network disconnects (e.g., wireless goes down, VPN disconnects,...). L7 then hangs and cannot be shut down any more. The CPU goes really high. The only way out is to force quit L7.

I use L7 on a Mac.

Armin

Armin,

We do have a case written up for this issue and the team will take a look at it.

Armin

https://community.logos.com/discussion/comment/857008#Comment_857008

I wonder if this case and the following two issues are all related:

https://community.logos.com/forums/t/133729.aspx

https://community.logos.com/forums/p/134208/876375.aspx