Bug 425920 - Runaway memory usage at startup
Summary: Runaway memory usage at startup
Status: REPORTED
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: 5.15.0
Platform: Other Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-08-28 20:59 UTC by Glen Whitney
Modified: 2020-08-28 20:59 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
standard output when running "korganizer" from the terminal prompt (958 bytes, text/plain)
2020-08-28 20:59 UTC, Glen Whitney
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Glen Whitney 2020-08-28 20:59:51 UTC
Created attachment 131253 [details]
standard output when running "korganizer" from the terminal prompt

KOrganizer uses an unlimited amount of memory, increasing up to and beyond 30GB (at which point it essentially hangs my system). This memory usage was tracked by LXTask 0.1.9; KOrganizer produced no graphical output during the memory buildup. (It did produce a bit of text to stdout, which I attach below in case it is of value.)


STEPS TO REPRODUCE
1. This is a OpenSUSE Tumbleweed system, kept regularly updated, mostly running XFCE with a few various apps from other desktops thrown in -- but without the full KDE  installed.
2. (It is probably worth noting that an earlier point, I did have KDE on the system, and tried KOrganizer using several calendars with at least hundreds of events, _maybe_ a thousand or two. However, I not only uninstalled KDE, I also deleted .kde*, .config/korga*, .config/akonadi*, .local/share/korg*, and .local/share/akonadi* -- so I certainly _attempted_ to restore KOrganizer to a "clean install" state. Of course, possibly I did not succeed, and if there are any suggestions of other files/configuration to eliminate to ameliorate the runaway memory usage, I would be glad to hear.)
3. Installed korganizer via "sudo zypper install korganizer."
4. Verified outcome of installation via "korganizer --version", which prints "korganizer 5.15.0 (20.08.0)"

OBSERVED RESULT
Starting korganizer from the shell produces the attached output to stdout; no window is shown; memory usage as reported by LXTask grows rapidly into the multiple gigabytes, bringing the machine to its knees after approximately five minutes.

EXPECTED RESULT
KOrganizer would start up, and display a window with its normal functions, using a reasonably normal amount of memory -- hopefully less than a few gigabytes.


SOFTWARE/OS VERSIONS
Linux: OpenSUSE Tumbleweed, running Linux 5.8.0-1
KDE Plasma Version: n/a; installed korganizer a la carte using zypper
KDE Frameworks Version: (not sure/how to check? -- whatever Tumbleweed is currently distributing)
Qt Version:  (ditto)

ADDITIONAL INFORMATION
This and Okular are the only KDE applications I have reinstalled after removing KDE entirely from the system a few months ago. (KOrganizer was definitely my favorite KDE app and I wanted to see if I could perhaps use it in an ecosystem of mainly non-KDE items. I installed Okular because there are few good PDF-processing applications available on Linux, and it runs without notable difficulty.) I am happy to provide further information if anyone reading this can suggest specific experiments to try or commands to post the output of. Thanks!