<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Multiple memory leaks in libmacabdrv1" href="https://bugs.documentfoundation.org/show_bug.cgi?id=111634#c24">Comment # 24</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Multiple memory leaks in libmacabdrv1" href="https://bugs.documentfoundation.org/show_bug.cgi?id=111634">bug 111634</a> from <a class="email" href="mailto:iplaw67@tuta.io" title="Alex Thurgood <iplaw67@tuta.io>"> Alex Thurgood</a> <pre>(In reply to Julien Nabet from <a href="show_bug.cgi?id=111634#c22">comment #22</a>) > Alex: do you have some link to explain more precisely how to run LO with > XCode? > Hi Julien, You don't need to build LO with XCode, indeed, I'm not even sure that you can (I managed once a very long time ago, but before the xcode-ide-integration script even existed - however, at the time, and it was completely by chance, I couldn't get any executable to run, so forget building with XCode). You don't need Xcode to use Instruments.app, but the reason I mention it in my reports is that Xcode includes a menu entry for developer tools that includes Instruments.app. However, as I found out recently, and as Telesto has indicated, you can find and start it directly by just typing Instruments into the Spotlight search function. Once Instruments has started, you can point it to your instdir tree as the target for analysis. Starting the recording (having previously selected the analytical tool of your choice (memory allocation, leaks, time profiling, stack/call tree, etc) will then automatically launch LODev.app in your /instdir, and close LO once you stop recording. I have to say that it is still a pretty slow process with a debug build, even with 8G RAM and 4 cores. Doing even the simplest of recordings can take 5 minutes or more each time.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>