https://bugs.kde.org/show_bug.cgi?id=333759
--- Comment #8 from Aetf <7437...@gmail.com> --- (In reply to Kevin Funk from comment #7) I am still not quite convinced (see below) but maybe the removal deserves it own patch. So, simpler fix submitted to Phabricator. For the "cache/duplicate" thing: I understand that we should avoid updating variables as much as possible due to communication costs. And that's what exactly the *thread_or_frame_changed* event handler for. Is there such a case that this handler is called without an actual change in active thread/frame? Given we now only check cached active thread/frame in this event handler, it looks duplicate to me. -- You are receiving this mail because: You are watching all bug changes.
