https://bugs.documentfoundation.org/show_bug.cgi?id=158914
Bug ID: 158914
Summary: Calc leaks RAM in response to any action
Product: LibreOffice
Version: 7.6.4.1 release
Hardware: ARM
OS: macOS (All)
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: Calc
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: al...@gtf.org
I'm currently using the latest 7.6.4.1 Apple Silicon release of LibreOffice
Calc on a Mac M1 Mini 16GB. It's kept up to date and currently running MacOS
Sonoma 14.2.1. That said, I've been experiencing what appears to be the same
issue for quite some time before realizing what was happening.
In short, Calc leaks vast amounts of memory during normal use until finally at
~9GB or so, it is running too slowly to use. At that point, I can save my work,
close (which takes minutes) or Force Kill Calc, and then start over. No data is
lost, but it's bizarre.
Initially I thought this was related to a particular document in which I was
often working. After more testing, it turns out that any document will behave
the same way. Even a fresh, empty Calc document on a freshly-started copy of LO
will exhibit the issue.
I can reproduce as follows:
1. Start LibreOffice
2. Under "Create:" on the left-hand menu, select "Calc Spreadsheet"
At this point, Activity Monitor shows 362.0 MB "Memory", 296.3 MB "Real Mem",
108.0 MB "Private Mem", and 77.7MB "Shared Mem". The numbers are stable as the
application sits, open on a blank sheet "Untitled 1".
3. Click on random cells in the empty document. Not moving around via scroll
bars, not typing anything, just selecting one cell and then another and
another. Not groups or anything, just moving the pointer and left-clicking.
I've now clicked about 50 times and see the following stabilized memory numbers
in Activity Monitor: 1005.0 MB "Memory", 956.0 MB "Real Mem", 750.3 MB "Private
Mem", 77.7 MB "Shared Mem". Once again these numbers are stable now that I'm no
longer clicking.
Once I start clicking again, the memory footprint resumes growing. In the case
of doing real work in a document, Calc will eventually become very slow and
ultimately unusable, after which the cycle above begins again.
A few things worth mentioning:
1. Writer does not exhibit any strange behavior.
2. No other application on the Mac (and I use it constantly) behaves strangely.
3. I do have Homebrew installed w/ various dev tools and whatnot.
4. I'm completely aware that this sounds crazy, and that it's surely tied to
something about my environment, but I haven't been able to identify it. Am
hoping perhaps there are diagnostics and logging that I can run to provide you
with additional information. It does seem to be a bug in Calc though, despite
being triggered by some unique(?) conditions.
--
You are receiving this mail because:
You are the assignee for the bug.
