<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <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#c77">Comment # 77</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 <a class="email" href="mailto:drJeckyll@Jeckyll.net" title="Ognian Tenchev <drJeckyll@Jeckyll.net>"> Ognian Tenchev</a> <pre>(In reply to <a href="show_bug.cgi?id=70924#c76">comment #76</a>) > (In reply to <a href="show_bug.cgi?id=70924#c74">comment #74</a>) > > 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. > > That sounds like an issue with memory fragmentation for a long running > system, would be my first guess. And difficult to test. It was up for no more than a day, but I guess it was "damaged" with old driver which crashed X. Or something like that may be :) > > But if I open let's say 5 or 6 large images, X freeze and then is killed > > with out of memory :) > > 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? Unfortunately no (:?) ... driver is not stripped and build with debug, but not with full debug. I will build it with full debug and post last messages here like before.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>