<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - UI: Writer crashes opening the style edit window after doing many style edits"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=126808#c11">Comment # 11</a>
on <a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - UI: Writer crashes opening the style edit window after doing many style edits"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=126808">bug 126808</a>
from <span class="vcard"><a class="email" href="mailto:jon@grossart.net" title="Jon Grossart <jon@grossart.net>"> <span class="fn">Jon Grossart</span></a>
</span></b>
<pre>I was able to create the crash again. There is no shortcut, you just have to
open and close a ton of dialogs until something stops working. It would
probably happen faster on a system with lower memory (I have 32 GiB). It might
be possible to record a macro to open and close the style window multiple times
to save on clicks.
WinDbg showed no exception at the time of crash, just a ton of runtime
exceptions that scroll basically any time you do anything in the program, but
the debugger doesn't stop then.
(2b04.1f44): C++ EH exception - code e06d7363 (first chance)
When the crash happened, the bugger did stop, but no real information showed up
in the analaysis.
However, proc explorer does show some interesting things:
9932 GDI handles -- when you start LibO with the same document opened I was
testing with, it shows 138 handles.
I don't think having 2 documents open should eventually end up with 2 GB of
working RAM with 8 GB of virtual size. Active RAM also went from 260 MB to 512
M
MB over the time of debugging. There is clearly some form of memory leak
happening.
For reference, just opening the same two documents with no editing:
Private Bytes: 421 MB
Peak Private: 1.15 GB
Virtual Size: 5.25 GB
Working Set: 260 MB
Hangles: 6559
GSI Handles: 178
USER Handlers: 229</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>