[Bug 92911] New: xorg resource leak and crash in Intel Ivybridge

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Nov 11 18:11:36 PST 2015


https://bugs.freedesktop.org/show_bug.cgi?id=92911

            Bug ID: 92911
           Summary: xorg resource leak and crash in Intel Ivybridge
           Product: DRI
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: mar.kolya at gmail.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 119581
  --> https://bugs.freedesktop.org/attachment.cgi?id=119581&action=edit
xorg log

X session crashes after some use, several times a day under normal desktop
usage.

I'll attach xorg log

I've noticed one more strange thing that is possibly related. Output of this
command:

cat /proc/{xorg pid}/maps  | grep mm | wc -l

(this looks for lines like this: 7fd313cc8000-7fd313d09000 rw-s 00000000 00:05
41728                      /drm mm object (deleted))

goes to 10's of thousands. It seems to be growing quicker if some videa
application is being used (google hangouts). Stopping browser (and hangouts)
doesn't seem to release those mmaps.

The frequency of the crashing seems to be roughly correlated to time of hangout
usage and therefore it looks like crashes and number of mmaps growing without
bounds seems related.

This all happens with current iobaf build on Ubuntu Trusty (Mint). Rolling back
to vivid lts packages seems to be keeping number of mmaped regions to less than
150 and no crashes so far.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20151112/f3c9bfe9/attachment.html>


More information about the intel-gfx-bugs mailing list