Skip to content

Editor-server can corrupt map file #123

@BlaiZephyr

Description

@BlaiZephyr
[2025-05-31T15:31:13Z INFO  fs] Found config dir in "/root/.config/ddnet-editor-server"
ALSA lib confmisc.c:855:(parse_card) cannot find card '0'
ALSA lib conf.c:5204:(_snd_config_evaluate) function snd_func_card_inum returned error: No such file or directory
ALSA lib confmisc.c:422:(snd_func_concat) error evaluating strings
ALSA lib conf.c:5204:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory
ALSA lib confmisc.c:1342:(snd_func_refer) error evaluating name
ALSA lib conf.c:5204:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5727:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2721:(snd_pcm_open_noupdate) Unknown PCM default

thread 'tokio-runtime-worker' panicked at game/game-base/src/datafile.rs:498:40:
mid > len
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

thread 'main' panicked at /root/ddnet-rs/lib/base-io/src/runtime.rs:53:38:
called `Result::unwrap()` on an `Err` value: JoinError::Panic(Id(318), "mid > len", ...)

thread 'main' panicked at /root/ddnet-rs/lib/base-io/src/runtime.rs:46:14:
called `Result::unwrap()` on an `Err` value: Could not find queue id 12 in {5: JoinHandle { id: Id(176) }, 2: JoinHandle { id: Id(7) }, 7: JoinHandle { id: Id(178) }}
stack backtrace:
   0:     0x5b6209b220ca - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::hfc616348d9ad0abc
   1:     0x5b6209b4e183 - core::fmt::write::h7ca648217bc79799
   2:     0x5b6209b1e033 - std::io::Write::write_fmt::h7960c58bfa5ccbcb
   3:     0x5b6209b21f12 - std::sys::backtrace::BacktraceLock::print::h3fb349e80cbe0423
   4:     0x5b6209b230c0 - std::panicking::default_hook::{{closure}}::h3366e5842cba645d
   5:     0x5b6209b22ea0 - std::panicking::default_hook::hd7573a5d4879884b
   6:     0x5b6209b23822 - std::panicking::rust_panic_with_hook::h66e909d048c263a9
   7:     0x5b6209b235ca - std::panicking::begin_panic_handler::{{closure}}::h8d9aa8be7e8634cf
   8:     0x5b6209b225d9 - std::sys::backtrace::__rust_end_short_backtrace::h7d7e47ef99abf6aa
   9:     0x5b6209b2325d - rust_begin_unwind
  10:     0x5b6208460740 - core::panicking::panic_fmt::hf8ffc7c15bfb58a0
  11:     0x5b6208460b76 - core::result::unwrap_failed::ha0269c4bdff93d7d
  12:     0x5b6208d42c8b - base_io::runtime::IoRuntimeTask<S>::wait_finished_and_drop::h5ecd79f72f2debb2
  13:     0x5b6208d40bba - core::ptr::drop_in_place<base_io::runtime::IoRuntimeTask<game_base::datafile::LegacyMapToNewOutput>>::h7f48693043efdb3d
  14:     0x5b6208d42bbf - base_io::runtime::IoRuntimeTask<S>::get_storage::h89626b04386fc33c
  15:     0x5b6208d2940d - map_convert_lib::legacy_to_new::legacy_to_new_from_buf::hfa6cdc11faec5b14
  16:     0x5b62089c7512 - editor::editor::Editor::load_map::h34fedcb4f517306b
  17:     0x5b62089cc71b - editor::editor::Editor::host_map::h08e21507d3b6956f
  18:     0x5b62084bcb97 - editor_server::main::hc932f1fd52111dc9
  19:     0x5b62084a6383 - std::sys::backtrace::__rust_begin_short_backtrace::he087ef2cfb011cb8
  20:     0x5b62084859d9 - std::rt::lang_start::{{closure}}::h882c2214e20b110b
  21:     0x5b6209b13ae7 - std::rt::lang_start_internal::heee0af441e41a6d2
  22:     0x5b62084bfa15 - main
  23:     0x79ef8e62a1ca - <unknown>
  24:     0x79ef8e62a28b - __libc_start_main
  25:     0x5b6208460e45 - _start
  26:                0x0 - <unknown>

thread 'main' panicked at library/core/src/panicking.rs:226:5:
panic in a destructor during cleanup
thread caused non-unwinding panic. aborting.
Aborted (core dumped)

quite interesting is the fact that the server had an uptime of ~20 days with no issues whatsoever - i randomly checked my VPS to see it being in a constant loop of crashing

a different mapfile works just fine - so i can only assume the mapfile is corrupted but the server had no person connecting for almost 4 days.

i pull from master fairly regularly and when i did pull master it ran fine - it happened during runtime..

Metadata

Metadata

Assignees

No one assigned

    Labels

    B - bugDang, that shouldn't have happened

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions