<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Crash using "Close" button for Extension Manager -> Check for Updates dialog"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=115420#c38">Comment # 38</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Crash using "Close" button for Extension Manager -> Check for Updates dialog"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=115420">bug 115420</a>
from <span class="vcard"><a class="email" href="mailto:michael.meeks@collabora.com" title="Michael Meeks <michael.meeks@collabora.com>"> <span class="fn">Michael Meeks</span></a>
</span></b>
<pre>Presumably the OpenGLSalGraphicsImpl (and other SalGraphicsImpls too) - and its
associated WinSalGraphics survives longer than the SalGeometryProvider which is
either a SalFrame or a SalVirtualDevice.
Then again the apparently deranged lifecycle of SalGraphics as they relate to
SalFrames etc. is something of a nightmare:
// SalGraphics or NULL, but two Graphics for all SalFrames
// must be returned
virtual SalGraphics* AcquireGraphics() = 0;
virtual void ReleaseGraphics( SalGraphics* pGraphics ) = 0;
So - working out what has failed to release the WinSalGraphics is probably
non-trivial; particularly as the bisection is reasonably unhelpful.</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>