<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [HD Graphics 4000] Segfault accessing rq->bo->handle" href="https://bugs.freedesktop.org/show_bug.cgi?id=91577#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [HD Graphics 4000] Segfault accessing rq->bo->handle" href="https://bugs.freedesktop.org/show_bug.cgi?id=91577">bug 91577</a> from <a class="email" href="mailto:fdo-bugs.aspseka@xoxy.net" title="Dominic <fdo-bugs.aspseka@xoxy.net>"> Dominic</a> <pre>Possibly. I experience a slow-down prior to the crashes. I am running xf86-video-intel trunk because of a memory leak in the last released version (on my machine, just opening specific applications (like java/Arduino-IDE) brought Xorg memory usage to >2GiB) This lead to X being oom-killed. Valgrind pointed to intel_drv.so. I did not investigate this further as this seems fixed on trunk. -- Just tested again. Indeed, Xorg is running out of memory: Just scrolling through aforementioned page in Links brings up Xorg memory usage a lot. Memory footprint is not going down after Links is closed and valgrind thinks it still is accessible. I don't suspect Links, I just chose it because it reliably (and quickly) exhibits this segfault. I am also seeing it working on gnome-terminal (less likely to crash) and Emacs (more so), but also "randomly".</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>