The Calendar View in the Digital Clock Plasmoid crashes when I open certain months. For example, it always crashes when I open September 2016 with my default calendar enabled. If I disable my default calendar and leave all the other calendars enabled, it does not crash. During September, when I tried to open the Digital Clock with my default calendar being enabled, it seemed as if the panel was opened invisibly. It changed the colour of the underlying window title bar. Sometimes, it simply crashes the plasmashell, but it also sometimes crashes the whole system. Reproducible: Always Steps to Reproduce: 1. Open Digital Clock Plasmoid 2. Navigate to September 2016 Actual Results: The plasmashell crashes, forcing me to restart it. Sometimes, it also renders the whole system unusable, forcing a whole reboot with hard reset. Expected Results: The Calendar View should display the events of September 2016. I have tried certain other months, and in a few of them, it also crashes. I don't really want to attach my calendar to it, and I also would prefer not to delete events in order to try and figure out which event caused this, but with a little guidance (log files, relevant source code), I could take a closer look into it, if that helps.
Small Update: After the 5.8 Update (5.8.2), the error still persists. I have managed to switch to a tty session while reproducing this bug and started htop. plasmashell had an unusually high cpu usage, which explains the slow mouse movement while this bug was active, but it had an especially enormous memory usage at around 16 (!) GiB. This also explains why this bug sometimes crashed my whole system. It looks like there might be some faulty allocation somewhere.
probably duplicate of #367541 is the PIM integration enabled?
(In reply to Marco Martin from comment #2) > probably duplicate of #367541 > is the PIM integration enabled? The PIM events plugin under "Settings for Digital Clock" -> Calendar? Yes, I have enabled this checkbox. But I only get the high memory usage when opening those certain months with certain calendars enabled (in the PIM Events Plugin settings), not all the time, so I think this is different to #367541, even though both might have the same reason.
For other reasons than this bug, I have reinstalled my whole system, and the error persists. I also have looked into KSysGuard to see what happens, but unfortunately, the system gets so unresponsive that I really could not do much. The memory usage goes up from about 300 MiB to 6,3 GiB where it seemed to stagnate, but then the whole plasmashell just crashed. I also have tried to analyse the memory footprint. There probably is some allocation loop that does not stop properly as the heap just explodes. You can see the heap just grow and grow. I tried to find some log output that maybe hints at what is going on, but I could not really find something useful. There are no errors in the journald logs, in the plasmashell logs, in the plasmashell output or in the akonadi logs, only warnings.
In https://bugs.kde.org/show_bug.cgi?id=367541 I have posted a backtrace [1] that i had obtained – maybe someone can make use of it. [1] https://bugsfiles.kde.org/attachment.cgi?id=102060
Created attachment 102354 [details] Stack trace of plasmashell crash after opening calendar in one of the affected months Stack trace of today, December apparently also is affected. It wasn't affected before, so some event or todo has been created that also causes this. I am running the latest KDE Applications and Framework, also kernel 4.8.7.1, distribution is Manjaro Linux 16.10 with the latest updates.
(In reply to kbrea from comment #6) > Created attachment 102354 [details] > Stack trace of plasmashell crash after opening calendar in one of the > affected months > > Stack trace of today, December apparently also is affected. > It wasn't affected before, so some event or todo has been created that also > causes this. I am running the latest KDE Applications and Framework, also > kernel 4.8.7.1, distribution is Manjaro Linux 16.10 with the latest updates. I meant to write November.
Is this still happening to you in Plasma 5.20?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!