https://bugs.documentfoundation.org/show_bug.cgi?id=115845
Timur <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|medium |low
CC|[email protected] |
Severity|normal |minor
--- Comment #13 from Timur <[email protected]> ---
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._______________________________________________
Libreoffice-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
