Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 09 Oct 2020 14:36:27 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 250226] graphics/drm-fbsd12.0-kmod: massive memory leak
Message-ID:  <bug-250226-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D250226

            Bug ID: 250226
           Summary: graphics/drm-fbsd12.0-kmod: massive memory leak
           Product: Ports & Packages
           Version: Latest
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: x11@FreeBSD.org
          Reporter: dinoex@FreeBSD.org
          Assignee: x11@FreeBSD.org
             Flags: maintainer-feedback?(x11@FreeBSD.org)

drm-fbsd12.0-kmod is 4.16.g20200221.

My desktop computer has 16 GiB RAM, but it seems that drm-fbsd12.0-kmod kee=
ps
leaking memory, using up all memory in one day and forcing me to reboot.

This computer uses Intel i5-6200U CPU and its integrated Intel Skylake
graphics.
The operating system is FreeBSD 12.1.

The version of drm-fbsd12.0-kmod is 4.16.g20200221.

When the system was just booted, wired memory was below 1 GiB.

top:
Mem: 3049M Active, 393M Inact, 174M Laundry, 981M Wired, 497M Buf, 11G Free
Swap: 16G Total, 16G Free

After the system had run for a few hours, wired memory became 14 GiB.
The desktop was still responsive, but the usage of swap was increasing.

After the system had run longer, wired memory become 16 GiB.
The desktop was non-responsive, even shell commands are frozen for 40 secs.

"vmstat -z" keeps stable:
1,392,114,304 TOTAL 1,333,297,844 58,816,460

See also:
https://github.com/FreeBSDDesktop/kms-drm/issues/247

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-250226-7788>