Search Issue Tracker


Under Consideration for 2021.3.X



Found in


Issue ID




[Linux] Crash on DisconnectGtkSignal(void*, GtkCallbackResponse (*)(), void*) when going through microgame tutorials



Reproduction steps:
1. Create a new 2D Platform or Lego microgame project
2. Go through the tutorial

Expected result: Unity Editor does not crash on all steps of the tutorial
Actual result: Unity Editor crashes

Reproducible with: 2021.3.16f1, 2021.3.23f1

Reproducible on: Ubuntu 22.04, Ubuntu 23.04, SteamOS, Arch, Linux Mint, Fedora, Manjaro, Pop OS

First lines of the stack trace:
#0 0x0056137151edcc in burst_signal_handler(int, siginfo_t*, void*)
#1 0x007f890dde4e60 in funlockfile
#2 0x007f890eba12fd in g_type_check_instance
#3 0x007f890eb96e7c in g_signal_handlers_disconnect_matched
#4 0x00561372b23123 in DisconnectGtkSignal(void*, GtkCallbackResponse (*)(), void*)
#5 0x00561372b0933e in OSOnRemoveMenuItem(MenuItem*)
#6 0x005613723c76bf in RemoveItemFromMenu(std::list<MenuItem, std::allocator<MenuItem> >*, core::basic_string_ref<char>)
#7 0x005613723c7713 in RemoveItemFromMenu(std::list<MenuItem, std::allocator<MenuItem> >*, core::basic_string_ref<char>)
#8 0x005613723c7553 in MenuController::RemoveMenuItem(core::basic_string_ref<char>)


# Usually, customers reproduce this on the “click Play” tutorial step
# Crashes with this stack trace were only reported in the 2021.3 LTS stream
# CQA couldn’t reproduce this crash on any of their Linux machines

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.