[Libreoffice-bugs] [Bug 115845] CPU usage increases randomly while writer is minimized after it has been open for several hours

[bugzilla-daemon at bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=115845

Timur <gtimur at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|medium                      |low
                 CC|gtimur at gmail.com            |
           Severity|normal                      |minor

--- Comment #13 from Timur <gtimur at gmail.com> ---
I find procdump useful in Windows when:
- WinDBG doesn't give result for any reason
- there's a dump but not a crash
- you need a simpler tool for end user compared to WinDBG that needs to be set

CPU may not be related to dump but it's worth trying. 
Usage is simple, without installation: 
- get Sysinternals free suite 
- run Cmd (Command Prompt)
- run LO (single version that you need)
- run procdump: path-to\SYSINTERNALSSUITE\procdump.exe soffice.bin -option
path-to\soffice.bin.dmp

"-option" is generally "-h" to write dump if process has a hung window and
that's what I use regularly 
But "-p" could be tried here, I didn't use it before. 
I guess we should have a wiki on this, which tool to use when. 

Dump is than analyzed in WinDBG via File-Open crash dump.

Missing in this bug is an example of document that gives consistent high CPU.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20180321/4d52a683/attachment.html>