[BUG] Logos 7 crashes if network connection changes

Member Posts: 1,520 ✭✭✭
edited November 2024 in English Forum

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

Welcome!

It looks like you're new here. Sign in or register to get started.

Comments

  • MVP Posts: 36,166

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

    Dave
    ===

    Windows 11 & Android 13

  • Member Posts: 1,520 ✭✭✭

    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 

  • MVP Posts: 36,166

    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.

    Dave
    ===

    Windows 11 & Android 13

  • Member Posts: 1,520 ✭✭✭

    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

  • Member, Logos Employee Posts: 4,597

    Armin said:

    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.

  • Member Posts: 1,520 ✭✭✭

    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

Welcome!

It looks like you're new here. Sign in or register to get started.

Welcome!

It looks like you're new here. Sign in or register to get started.