https://bugs.kde.org/show_bug.cgi?id=489644
--- Comment #7 from RedBearAK <redb...@redbearnet.com> --- (Had a "mid-air collision" with your comment when I tried submit this a minute ago.) Slightly nuanced addition. I'm having a hard time going back to the RPM version to check this because for some reason the Flatpak version replaced the instance of Text Editor in the launcher menu. Even Ulauncher doesn't show more than one "Text Editor", and when I launch it it's the Flatpak version. Anyway, with the Flatpak I can revert the CPU usage by simply selecting some new text, yet if I then unselect that new text (without deleting it while selected), the high CPU usage immediately returns. Until I select text again. There's no cutting/copying or deleting involved in this case. Just selecting. But now, attempting to select text and copy it, avoid deleting it, then continue typing, the high CPU usage also still comes right back. So once this cycle starts it appears to want to continue until the app quits. The dialog about Plasmashell crashing has never shown up so far with the Flatpak, even though I've done the same process of causing the high CPU usage and then quitting the app quite a few times. It was usually about 50/50 with the crash dialog while using the RPM version of the app. -- You are receiving this mail because: You are watching all bug changes.
