Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. Dismiss Notice

Bug 2019 Editor keeps crashing on startup

Discussion in 'Linux' started by LoneGoat, Jul 19, 2023.

  1. LoneGoat

    LoneGoat

    Joined:
    Dec 16, 2020
    Posts:
    21
    Issue
    I revisited a project I had not touched for many months today and could not get the Unity Editor to open. Upon some digging I found a log containing many GTK-Crital errors. I installed this editor version (2019.4.2) back in January and used it without issue for 2 months. Since it has been untouched till today, I cannot see how Unity is to blame.

    Any advice or trouble shooting steps or paths to investigate would be appreciated. I'm a novice Linux user, in that I can generally find logs for crashes :smile: but not much else.

    The Gnome folk have of course disavowed any thought that this might be a gtk issue, but I just don't see how this is a Unity issue....

    Steps to reproduce
    1. Install Unity 2019 Editor
    2. Open Editor
    3. Silent crash

    Version information
    I am using an up to date Fedora 38 install, default GTK install. I have tested with Unity 2019.4.2, 2019.4.28, and 2019.4.40 (last release).
    I did a OS version upgrade in the timeline somewhere (don't quite remember when) from 37 to the current 38.

    I have a dual gpu laptop and have tested this on the amd and nvidia gpu's in Wayland (default) and Xorg.

    Warnings
    Application crashes silently.

    Editor log (at
    ~/.config/unity3d/Editor.log
    ) is normal except that there is between 1 and 30 instances of:

    (Unity:18080): Gtk-CRITICAL **: 23:17:41.795: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed


    that cut short at:
    ../../third_party/tcmalloc/chromium/src/tcmalloc.cc:289] Attempt to free invalid pointer 0x55a77dfc1570


    and sometimes end with:
    Parent process [22965] was terminated


    Backtrace
    See the attached log for the best I have been able to do using `gdb`
     

    Attached Files:

  2. LoneGoat

    LoneGoat

    Joined:
    Dec 16, 2020
    Posts:
    21
    Well I found some more info from a kind soul on the Gnome Discourse server.

    Turns out this is a problem with OpenGL compatibility. If I manually open the ProjectSettings.asset file and switch the Linux player to the Vulkan renderer manually the editor will launch!

    Code (Boo):
    1.  
    2.   - m_BuildTarget: LinuxStandaloneSupport
    3.     m_APIs: 1500000011000000
    4.     m_Automatic: 0
    5.  
    So there is some sort of compatibility issue between the 2019 editor and the current (I assume mesa) OpenGL...
     
    unity_ZTQlqtep9ZGQVw likes this.
  3. tylerinthezoo

    tylerinthezoo

    Unity Technologies

    Joined:
    Jun 15, 2022
    Posts:
    82
    i would highly suggest upgrade to LTS since they receive the latest support.
     
  4. LoneGoat

    LoneGoat

    Joined:
    Dec 16, 2020
    Posts:
    21
    Well yes, that's the ideal. But the version isn't up to me.

    I'm pushing for that option.
     
    tylerinthezoo likes this.