Closed naglis closed 3 years ago
After additional testing, the same assertion error is triggered if state_file_interval
or restore_paused
are set to an empty or an invalid value (e.g. state_file_interval ""
, restore_paused ""
, state_file_interval "-1"
, restore_paused "?"
). Should I create separate issues for these?
One issue is ok, this is the same bug - when C++ unrolls the stack during failed startup, MPD doesn't properly destruct everything.
Bug report
Describe the bug
MPD crashes due to an assertion error on startup if
state_file
configuration option is empty (state_file ""
) or is not an absolute path (e.g.state_file "foo"
).Expected Behavior
MPD logs a warning if the config value is invalid (and ignores it or exits), but does not crash.
Actual Behavior
MPD crashes.
Version
Log
Backtrace
Config