https://bugs.kde.org/show_bug.cgi?id=410596
David Jarvie <djar...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|REPORTED |CONFIRMED
--- Comment #9 from David Jarvie <djar...@kde.org> ---
Yes, there is a bug in removeKAEvents, and your patch looks good. I'll wait for
you to submit it in Phabricator.
The valgrind trace shows that a calendar added is being processed, and that
that is interrupted (while a 'new' is being executed) by the removal of a
calendar, and that in turn is interrupted (while a 'delete' is being executed)
by another removal of a calendar.
Obviously valgrind makes this more likely to happen since the code runs slower,
but it could potentially still happen in normal use. The code in AlarmCalendar
is not designed to work in such circumstances (for example, removeKAEvents
deletes each KAEvent instance individually before references to them are
finally all removed from mResourceMap), so a queuing mechanism is needed.
--
You are receiving this mail because:
You are watching all bug changes.
