NetBSD-Users archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: wired memory leak?
On Mon, Nov 02, 2026 at 11:05:57AM +0100, Havard Eidnes wrote:
> >> Is this with the `modesetting' DDX driver? Because, if I use the `intel' Xorg
> >> driver, all wired memory is reclaimed. The downside is that the `intel' driver
> >> is old, obsolete, and crashed the kernel when I did a kernel compile while
> >> watching the pretty fishies[1].
> >
> > All my systems uses the intel driver (AFAIK modesetting doesn't support
> > multiple displays output)
>
> Well, I'm using two screens: one 3440x1400, one 2560x1440, and it
> appears that I'm using the "modesetting" driver, ref. Xorg.0.log:
>
> [ 6279.383] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
> [ 6279.383] (--) Using wscons driver
> [ 6279.399] (**) modeset(0): claimed PCI slot 0@0:2:0
> [ 6279.399] (II) modeset(0): using default device
> [ 6279.399] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
>
> etc. etc.
OK so maybe I didn't try hard enough. Also I started doing multi-display
on this machine with netbsd-9, maybe even netbsd-8
> [...]
>
> But ... I'm also observing an excessive amount of "Wired" memory
> on this host, which has 32GB physical memory, "top" says:
>
> load averages: 1.46, 1.05, 2.20; up 14+01:23:00 10:50:34
> 209 processes: 1 runnable, 207 sleeping, 1 on CPU
> CPU states: 0.1% user, 0.0% nice, 0.1% system, 0.0% interrupt, 99.6% idle
> Memory: 1787M Act, 321M Inact, 19G Wired, 263M Exec, 1550M File, 2856M Free
> Swap: 32G Total, 1317M Used, 31G Free / Pools: 6457M Used / Network: 38K In, 24
>
> It is usually running firefox, but this is with firefox killed,
> and the excessive "Wired" amount persists beyond firefox running.
Yes this is what I've been seeing too. Even killing X didn't free the
wired memory.
--
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
NetBSD: 26 ans d'experience feront toujours la difference
--
Home |
Main Index |
Thread Index |
Old Index