https://bugs.documentfoundation.org/show_bug.cgi?id=159175
Patrick Luby (volunteer) <guibomac...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
--- Comment #12 from Patrick Luby (volunteer) <guibomac...@gmail.com> ---
(In reply to Patrick Luby (volunteer) from comment #11)
> Created attachment 194758 [details]
> Snapshot of Instruments applications with Allocations List sorted highest to
> lowest
>
> Version: 25.2.0.0.alpha0+ (AARCH64) / LibreOffice Community
> Build ID: fab293ebc59c583f4cd17a6802f7d538b6b53556
> CPU threads: 8; OS: macOS 14.5; UI render: Skia/Raster; VCL: osx
> Locale: en-CA (en_CA.UTF-8); UI: en-US
> Calc: threaded
So I ran the Instruments application's memory leak tool against my local debug
master build. I launched LibreOffice, and started tracking in Instruments when
the Start Center appeared. Then, I open 10 empty Calc documents and stopped
tracking in Instruments.
I found no big memory leaks, but memory usage when I stopped tracking in
Instruments was over 2 GB. So I sorted the "Allocations List" to see the
highest memory allocators as shown in the snapshot in attachment #194758. Not
surprisingly, the highest allocators look like they are bitmaps and/or drawing
surfaces for each window.
Not sure what all this data points to yet. But what seems odd to me is that all
of the highest allocators are a lot larger than I expected. Window sizes during
my test were roughly 1500 x 1000 pixels. Double both and multiply for Retina
display (i.e. each Retina pixels is really 4 pixels) and by 4 since each pixel
is 32 bits and, if my math is correct, I would expect to see roughly 24 MB for
each window's internal backing bitmap or roughly 240 MB for 10 windows. Double
that to 480 MB because LibreOffice has its own backing bitmap for each window.
So I can account for roughly 0.5 GB of the memory usage by see 2 GB of total
memory usage.
When I get some time, I think the next step that I need to do is figure out
what is in the remaining 1.5 GB of memory usage.
--
You are receiving this mail because:
You are the assignee for the bug.
