<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Xorg memory leak with >=xf86-video-intel-2.99.901 and above"
href="https://bugs.freedesktop.org/show_bug.cgi?id=70924#c76">Comment # 76</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Xorg memory leak with >=xf86-video-intel-2.99.901 and above"
href="https://bugs.freedesktop.org/show_bug.cgi?id=70924">bug 70924</a>
from <span class="vcard"><a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> <span class="fn">Chris Wilson</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=70924#c74">comment #74</a>)
<span class="quote">> I have a question.
>
> Can kernel update from 3.12-rc7 to 3.12 correct corruption? Or can it be
> something between kernel and driver to cause corruption?</span >
3.12-rc7 to 3.12, not that I am aware of - I didn't send any fixes.
<span class="quote">> I'm still running driver from commit
> 8f6e227ba8127a2ca034271f2a660c24abbe056f, which before kernel upgrade and
> reboot produce corruption after I open large image.
>
> Now I can't reproduce this. After opening couple of large images (one by one
> - open one, close it, open another one, close it) there is no corruption.</span >
That sounds like an issue with memory fragmentation for a long running system,
would be my first guess. And difficult to test.
<span class="quote">> But if I open let's say 5 or 6 large images, X freeze and then is killed
> with out of memory :)</span >
Meh, still hitting recursion. Any chance you can capture that with debug
symbols?
Does 'addr2line -e /usr/lib/xorg/modules/drivers/intel_drv.so -i 0x1f62d'
resolve to anything useful?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>