Summary: | PIM events in Plasma calendar causes OOM killer | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Martin Ottmar <mirovski36> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | plasma-bugs |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | plasmashell console output |
Description
Martin Ottmar
2019-07-25 08:03:15 UTC
Please can you run QSG_INFO=1 plasmashell and paste the output. Please move your ~/.config/plasma-org.kde.plasma.desktop-appletsrc and see if that makes a difference. Finally can you run kcmshell5 qtquicksettings and select the software renderer and see if that makes a difference. Created attachment 121737 [details]
plasmashell console output
(With the current configuration): Running with the software renderer doesn't make any difference. Even with compositing completely turned off. After the "configuration reset", plasmashell starts immediately with the "usual" size in memory, but... Today I've noticed that just after boot, the plasmashell was running with the "usual" portion of memory. But, it was killed by OOM killer after 22 minutes of uptime. If I remember well, the progress was the same yesterday in the morning. The first killing occurred after some amount of time, but each (working) day, I'm using my system exactly the same way. So, I'm going to try to configure plasma again, as it was before the configuration reset and to watch its behaviour carefully. For now, thanks for Your interest and I'm sorry for my bad English. BTW: what does the "Tokenizer Warning: 8Bit character" message mean? I mean, how to distinguish, from where it comes from? I've noticed it before within restarting akonadi (when I was fighting with akonadi problems). I'm using UTF-8 within the whole system It seems that the problem won't appear until I enable "PIM events plugin" in settings of digital clock applet. When I enable "PIM events plugin" option, there are missing calendars to choose at all in the side "tab", but at the moment, akonadiserver, mysql and akonadi_imap_resource_3(?!) start to exhaust CPU for a lot of minutes. And RAM allocated for plasmashell starts to grow slowly (cca 200kB per second?). And then, let's say, after cca 10minutes (probably just when akonadi_indexing_agent starts) the consumed memory skyrokets up to 2GB... If there is enough of free memory and OOM killer leaves plasmashell running, then CALDAV calendar events finally appear in the digital clock calendar, and akonadi stops draining CPU. This akonadi behaviour is new too. Ok, please file a bug with this information to akonadi. I don't think we can do much from the plasma side. 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! Thank you for reporting this crash in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the crash with a recent software version? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you! Oh, I'm sorry. I've tried to enable the digital clock PIM plugin few weeks ago, and it didn't crash. PIM started immediately, with working kalendar and containing valid PIM informations. There is not any CPU or (noticeable) memory impact on plasmashell. There is nice new feature like dots as events by each day. At least dots by the first visible day (of each month page) have invalid color, but damn it! Digital clock caPIM events work again within daily using! But I don't know, when it was fixed. The last unsuccessful try before, it was probably last year. I think, this ticket should be closed. Plasma: 5.25.5 Frameworks: 5.98.0 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! |