https://bugs.documentfoundation.org/show_bug.cgi?id=158397
--- Comment #16 from Telesto <[email protected]> --- (In reply to Patrick Luby (volunteer) from comment #14) > Sorry, but I don't know how to unpack this. Seems you want me to lean on > (i.e. guilt) someone I've never met to work on your bug. No thanks. Typical > "all hands on deck for my bug" behavior. Well I might not have realized how this could be perceived/interpreted. Is surely not my idea to force you to work with someone else or to guilt someone else also working on this. Most developers have so expertise area. This is somewhat is his area. So if you need help...; which is quite suggestive and premature. I shouldn't have kept my mouth shut, IMHO. Dev e-mail list probably better place anyhow. > What really catches my eye is that you reported this bug 6 months ago and > during all of that time, you could've run an Instruments CPU Profile. I > still remember the shit I went through to enable connecting to LibreOffice > to Instruments over a year ago. Yet, zero interest in using Apple's amazing > leak and CPU usage tool. > Six month and no one has bothered to fire up the Instruments application. > But now I need to run around and ask for everyone's input because apparently > I'm not moving fast enough. I do use the Instruments application once in a while. I'm grateful you a enable connecting to LibreOffice. However it feels bit as random posting screenshots if you not 100% convinced about what you're doing. Drill down the list until until the last item in the stack with high CPU time spend It also a kind of a snapshots, which can age very quickly. It feels bit pointless task if nobody takes a look. But if you prefer so to have instruments sreenshot before CC, I will do. > I'll fix it when I fix it. There is no rush; the bug is present for years. -- You are receiving this mail because: You are the assignee for the bug.
