Stim/Response Editor causes total DarkRadiant Crash

[Jnon]

I'm running DarkRadiant 3.9.1 in Ubuntu 22.04.4 LTS (jammy), installed from orbweaver's PPA. I originally installed it when my OS was 20.04 (focal), and at the time everything worked as expected. I want to say that the Stim/Response Editor worked as normal back then, because I remember using it at least once with no issue, though in all honesty I rarely touch it.

Following an OS upgrade to jammy, I updated the orbweaver repositories in my /etc/apt/sources.list.d (from focal to jammy) and everything seemed okay.. ran updates, tested DarkRadiant, everything worked. Right up until I tried opening the Stim/Response Editor, and then the whole program crashes. I tested this with multiple maps, large and small, and the results are always the same. I feel that the upgrade from focal to jammy broke something, but I can't say that with any certainty.

Error log is enclosed:

ASSERT INFO:
../src/gtk/dataview.cpp(372): assert "iIndex != (-1)" failed in Remove(): removing inexistent element in wxArray::Remove

BACKTRACE:
[1] wxDataViewModel::ItemDeleted(wxDataViewItem const&, wxDataViewItem const&)
[2] wxDataViewModelNotifier::ItemsDeleted(wxDataViewItem const&, wxDataViewItemArray const&)
[3] wxDataViewModel::ItemsDeleted(wxDataViewItem const&, wxDataViewItemArray const&)
[4] wxutil::TreeModel::Clear()
[5] StimTypes::reload()
[6] ui::StimResponseEditor::ShowModal()
[7] ui::StimResponseEditor::ShowDialog()
[8] cmd::CommandSystem::executeCommand(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::vector<cmd::Argument, std::allocator<cmd::Argument> > const&)
[9] cmd::CommandSystem::execute(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)
[10] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&)
[11] wxEvtHandler::SearchDynamicEventTable(wxEvent&)
[12] wxEvtHandler::TryHereOnly(wxEvent&)
[13] wxEvtHandler::ProcessEventLocally(wxEvent&)
[14] wxEvtHandler::ProcessEvent(wxEvent&)
[15] wxEvtHandler::SafelyProcessEvent(wxEvent&)
[16] wxMenuBase::SendEvent(int, int)
[17] g_closure_invoke
[18] g_signal_emit_valist
[19] g_signal_emit
[20] gtk_widget_activate
[21] gtk_menu_shell_activate_item
[22] g_signal_emit_valist
[23] g_signal_emit
[24] gtk_main_do_event
[25] g_main_context_dispatch
[26] g_main_loop_run
[27] gtk_main
[28] wxGUIEventLoop::DoRun()
[29] wxEventLoopBase::Run()
[30] wxAppConsoleBase::MainLoop()
[31] wxEntry(int&, wchar_t**)
[32] __libc_start_main

Spoiler

 

 

[OrbWeaver]

I can reproduce the issue with the PPA version on Ubuntu 22.04.

Unfortunately it does not reproduce in a local debug build. Actually it does, it's just that the assertion message only appears in the console after I changed the handler for wxWidgets assertions, due to repeated assertions from within the wxWidgets art provider which we cannot do anything to fix.

[Jnon]

19 hours ago, OrbWeaver said:

repeated assertions from within the wxWidgets art provider which we cannot do anything to fix

Is this exclusive to the PPA version? If I uninstalled it and moved to the Flatpak (or compiled from source, I guess) would that remove the issue? Or would Ubuntu Jammy be hostile to the Stim/Response editor regardless?

I can keep using DarkRadiant without a Stim/Response editor if I have to, but I'd like to have the option if possible.

[OrbWeaver]

Given that the same issue reproduces in a local debug build, I don't think the issue is specific to the PPA build. But you're certainly welcome to try the FlatPak version to see if it behaves differently.

[Jnon]

Just to follow up on this, the darkradiant / darkradiant-plugins-mod just updated (to v3.9.2), and the Stim/Response Editor now no longer crashes. So that's good. Whoever fixed it, thank you.
 

[OrbWeaver]

Thanks for confirming the latest version fixes the issue.

Note that you can see all of the changes for a new package by viewing the changelog:

$ zless /usr/share/doc/darkradiant/changelog.gz