https://bugs.kde.org/show_bug.cgi?id=437364
--- Comment #39 from Fabian Vogt <fab...@ritter-vogt.de> ---
(In reply to Fabian Vogt from comment #38)
> (In reply to Fabian Vogt from comment #37)
> > For some reason this now started to fail in openQA tests which upgrade from
> > 5.8/5.12/5.18 (Leap 42.x/15.x) -> 5.24 (Tumbleweed). First, kglobalacceld
> > crashes and after the automatic restart the situation is as outlined in this
> > report: Two entries in kglobalshortcutsrc which don't work. At least in
> > openQA this looks like it's reproducible. Unfortunately I wasn't able to get
> > a backtrace, but it seems to be heap corruption ("unaligned fastbin chunk
> > detected"). The crash is not reproducible manually at least.
> >
> > This matches the arrival of Frameworks 5.97 in Tumbleweed. I can't tell how
> > much 5.97.0 actually caused this or just exposed it more...
> >
> > CC Ahmad, who did the majority of changes in kglobalaccel 5.97.
>
> It's actually fairly simple: kglobalacceld crashes when the kconf_update
> binary runs. With valgrind, the cause is obvious:
"obvious" - ha! I wrote too soon.
~Component actually calls registry->takeComponent so it modifies m_components.
The subtle addition of "&" in the QHash -> std::vector commit means that the
container
being iterated gets changed underneath the method. Just removing the "&" again
doesn't
fix the crash though, it just crashes differently, taking valgrind with it...
Needs a closer look.
--
You are receiving this mail because:
You are watching all bug changes.
