https://bugs.documentfoundation.org/show_bug.cgi?id=99784
--- Comment #39 from Alex Thurgood <[email protected]> ---
(In reply to Michael Meeks from comment #38)
> Hi Alex; I watched the video - it shows the memory increasing - which in
> itself is interesting - but unfortunately doesn't give us a good idea of
> where those memory allocations actually come from =) Can we not use the tool
> to explore what the stack trace of those allocations is ? ie. where in the 8
> millions lines does it come from (it could be in the extension too FWIW ;-).
> Without that this is very much a "something leaks" type report.
>
> Thanks !
Hi Michael,
That is precisely what the Instruments.trace file is for. It contains a
hierarchical tree list of all calls made, but as far as I can tell, you can
only exploit this file via the Instruments.app. In reality, the trace file is a
compressed folder containing various objects that Instruments.app knows how to
read and display and allows the user to pinpoint the calls being made at any
given point along the profile. If the trace is coupled to symbols and source
code, which it can be, and which I haven't undertaken, one can apparently
examine the code path in even greater detail, but all of that is beyond me, I'm
afraid.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
