Crash when re-scanning library (v3.52.0)

[stkw0]

While manually scanning the library lms crashed. I was using lms v3.52.0 with taglib version 1.13.1 (in case it's relevant).

[mp3 @ 0x7f8f2c02c380] Estimating duration from bitrate, this may be inaccurate
TagLib: ID3v2.4 no longer supports the frame type RVAD. It will be discarded from the tag.
TagLib: ID3v2.4 no longer supports the frame type RVAD. It will be discarded from the tag.
TagLib: ID3v2.4 no longer supports the frame type RVAD. It will be discarded from the tag.
TagLib: ID3v2.4 no longer supports the frame type RVAD. It will be discarded from the tag.
TagLib: ID3v2.4 no longer supports the frame type RVAD. It will be discarded from the tag.
TagLib: ID3v2.4 no longer supports the frame type RVAD. It will be discarded from the tag.
TagLib: ID3v2::Tag::read() - Duplicate ID3v2 tags found.
TagLib: ID3v2::Tag::read() - Duplicate ID3v2 tags found.
TagLib: ID3v2::Tag::read() - Duplicate ID3v2 tags found.
TagLib: ID3v2::Tag::read() - Duplicate ID3v2 tags found.
TagLib: ID3v2::Tag::read() - Duplicate ID3v2 tags found.
TagLib: ID3v2::Tag::read() - Duplicate ID3v2 tags found.
TagLib: ID3v2::Tag::read() - Duplicate ID3v2 tags found.
TagLib: ID3v2::Tag::read() - Duplicate ID3v2 tags found.
/usr/lib/gcc/x86_64-pc-linux-gnu/13/include/g++-v13/optional:486: constexpr const _Tp& std::_Optional_base_impl<_Tp, _Dp>::_M_get() const [with _Tp = lms::scanner::ScanStepStats; _Dp = std::_Optional_base<lms::scanner::ScanStepStats, true, true>]: Assertion 'this->_M_is_engaged()' failed.
Magick: abort due to signal 6 (SIGABRT) "Abort"...

I have automatic scanning scheduled each day and I updated some days ago, today I added more songs, maybe some new files produce this crash¿?

In a couple of days I will recompile it with debugging symbols and provide more info as I guess it will be probably not be enough with this.

[epoupon]

Thanks for reporting!
Is it the docker version? If not, which OS?

[stkw0]

It was on Gentoo, though I see it is already fixed¿?

[epoupon]

Yes I think it should be fine now! If that bothers you you can cherry pick the associated commit.