[Wesnoth-bugs] [bug #24022] Crash on Quit Scenario With Planned Recruits Present

Follow-up Comment #2, bug #24022 (project wesnoth): Does it provide any additional information about the crash? It's possible the MSVC++ runtime is detecting something that GNU libstdc++ would normally ignore and cause harder to debug situations later on (e.g. memory corruption).

[Wesnoth-bugs] [bug #23893] attempt to add an [event] with empty id=, ignoring

Update of bug #23893 (project wesnoth): Status:None => Invalid ___ Follow-up Comment #1: You seem to have at least one [unit_type][event] without an id=. For such [event]s id= is

[Wesnoth-bugs] [bug #23893] attempt to add an [event] with empty id=, ignoring

Update of bug #23893 (project wesnoth): Assigned to:None => anonymissimus ___ Reply to this item at: ___ Nachricht

[Wesnoth-bugs] [bug #24022] Crash on Quit Scenario With Planned Recruits Present

Follow-up Comment #1, bug #24022 (project wesnoth): Correction: this seems to be on Windows only. Possibly even MSVC-build only, the crash is within the MS implementation of the std::deque object of fake_unit_manager::remove_temporary_unit().

[Wesnoth-bugs] [bug #24020] almost (?) reproducible complex crash involving the whiteboard

Follow-up Comment #2, bug #24020 (project wesnoth): I could also reproduce this on 1.13.1+dev with only 2 sides which are not allied (removed side 2 of previous example and let side 1 and 3 be enemies) I wonder whether the crash is caused by the error from the stderr.