Alexander Barcza <ab...@cam.ac.uk> writes: >> If you have access to a binary with debug information and to the >> Shark.app profiler, it would be interesting to know what parts of LyX >> are causing the cpu load.
> I'd be pleased to help but not a developer. Shark.app is installed and if > you give me a quick description of what you are interested in I can run > Shark the next time this scenario repeats. I don't know when that will be > because as I said just reopening the file doesn't lead to the high cpu load. It may be a bit complicated to explain if we do not know when it happens. Basically, you launch shark.app, click on 'start' (I am not sure when the button name is, but there is only one :), and wait until it has finished (30 seconds or something like that). Then it shows you a window with the list of functions/methods where cpu time is spent. However, in practice it is a bit difficult to master, so the best you can do is probably to try to understand what puts LyX in this situation. JMarc
