Follow the steps in https://bugs.documentfoundation.org/show_bug.cgi?id=95582#c0 Leave the document open and get you some nice cup of herbal tea ;) and a break. After some .. 10 - 15 - minutes, the van starts to blow and my system monitor reveals 50% of total CPU = 100% of one CPU. Some sys info: description: Computer width: 32 bits capabilities: smbios-2.6 *-core description: Motherboard physical id: 0 *-memory description: System memory physical id: 0 size: 3945MiB *-cpu product: Genuine Intel(R) CPU U7300 @ 1.30GHz vendor: Intel Corp. physical id: 1 bus info: cpu@0 version: 6.7.10 serial: 0001-067A-0000-0000-0000-0000 size: 1300MHz capacity: 1300MHz width: 64 bits capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx x86-64 constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm dtherm tpr_shadow vnmi flexpriority cpufreq configuration: id=0 *-logicalcpu:0 description: Logische CPU physical id: 0.1 width: 64 bits capabilities: logical *-logicalcpu:1 description: Logische CPU physical id: 0.2 width: 64 bits capabilities: logical
calgrind would be useful here :)
(In reply to Joel Madero from comment #1) > calgrind would be useful here :) this https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_Valgrind_log ?
(In reply to Cor Nouws from comment #2) "install the valgrind package" from where ?
I'm working on the calgrind - poke me in a few days if I haven't attached something :)
I see no spike at all in CPU - opened for 15 minutes now so I can't get a log. Sorry!
(In reply to Joel Madero from comment #5) > I see no spike at all in CPU - opened for 15 minutes now so I can't get a > log. Sorry! Thanks for trying Joel. Can you answer comment #2 and #3 please?
@Cor - I'm probably not the best person to ask as I barely understand this stuff myself but: 1) You can install valgrind from your package manager - for instance ubuntu is just sudo apt-get install valgrind 2) To run it (the wiki needs some real love from documentation team as it's overly complicated) valgrind --tools=callgrind ./soffice.bin <filename> that'll create new log files (several). Look for the largest file as it's most likely the right one
(In reply to Joel Madero from comment #5) > I see no spike at all in CPU - opened for 15 minutes now so I can't get a > log. Sorry! I linked to the wrong file :\ Sorry for that! The file giving the problem is this one https://bugs.documentfoundation.org/attachment.cgi?id=120438 I'll try a valgrind myself
Created attachment 120446 [details] log valgrind Not that much spectacular this time, I think. Anyway, no full cpu usage. Would it possibly make sense to follow (one of) these: ==4181== Rerun with --leak-check=full to see details of leaked memory ==4181== Use --track-origins=yes to see where uninitialised values come from ??
The document opens fast in Version: 5.5.0.0.alpha0+ Build ID: 6ab249ea6aecef5d3f35d624622a368061cad9c3 CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); Calc: group Could you please try to reproduce it with the latest version of LibreOffice?
(In reply to Xisco Faulí from comment #10) > The document opens fast in The report is not about the time of opening, but what happens after 10-15 minutes. But tried that again in a recent daily, and no problem any more. So WorksForMe. thanks for asking,