Memory leaks from swapper, wpa_supplicant, glxgears

Memory leaks from swapper, wpa_supplicant, glxgears

[Daniele C.]

[-- Attachment #1: Type: text/plain, Size: 1074 bytes --]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello there,

I have enabled CONFIG_KMEMLEAK and I am finding some memory leakage apparently caused by "swapper" process; I have also had leaks from glxgears and wpa_supplicant, but they can be triggered only once (e.g. restarting wpa_supplicant does not trigger more leaks).

The swapper leaks seem to be an incremental decimal string, starting from "0" to "10", while the wpa_supplicant leaks were the AP ESSID (not in attached report).

Best regards,
- -- 
  Daniele C.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJLrL1xAAoJEON28As9epPApycIAJpEURXnySLJS7P8NvTSs42e
G+2iajFLSAyyQdnKlWI41+ciSe5XsYFtag8xpgS2qPvLcwmEEMo95sUrMQExtw6h
hre4O/T0N6W4x86rEvefAwMn73nYDGoV2fcx5GHpfmyyc7Mm8+gNPzcoAicLSjh4
MRqny9S/AyBIhGBh3nobldDiFzCvD4WmNZM0jPcNCZwQZfO7FJnjXwwEU9epjM/9
4+HaVk8lt4gNrSNIx9yPN2oqNxyZBv5ySs6l8ukr0cozLSq0MrzMjlwnwB+FfQqg
cmcTHYPA16FNu5Y4CoYXm8DlLj1RVFuNGlyy6WQpc7eRuiZeO9MpJOFSFZPHdlA=
=VSaD
-----END PGP SIGNATURE-----

[-- Attachment #2: swapper_memleaks.txt --]
[-- Type: text/plain, Size: 3646 bytes --]

unreferenced object 0xdf0a6540 (size 192):
  comm "swapper", pid 1, jiffies 4294667841 (age 877.335s)
  hex dump (first 32 bytes):
    00 00 00 20 ff ff bf fe f0 9d 12 df 00 02 00 00  ... ............
    68 65 0a df 6c 65 0a df 00 00 00 00 20 a9 0c c1  he..le...... ...
  backtrace:
    [<ffffffff>] 0xffffffff
unreferenced object 0xdf129df0 (size 16):
  comm "swapper", pid 1, jiffies 4294667841 (age 877.335s)
  hex dump (first 16 bytes):
    50 43 49 20 42 75 73 20 30 30 30 30 3a 30 30 00  PCI Bus 0000:00.
  backtrace:
    [<ffffffff>] 0xffffffff
unreferenced object 0xdf242040 (size 16):
  comm "swapper", pid 1, jiffies 4294668193 (age 876.985s)
  hex dump (first 16 bytes):
    70 6e 70 20 30 30 3a 30 34 00 00 00 ff ff ff ff  pnp 00:04.......
  backtrace:
    [<ffffffff>] 0xffffffff
unreferenced object 0xdf21a2a0 (size 32):
  comm "swapper", pid 1, jiffies 4294668193 (age 876.985s)
  hex dump (first 32 bytes):
    00 00 c1 fe ff ff c1 fe 40 20 24 df 00 00 00 00  ........@ $.....
    bc f8 5a c1 00 00 00 00 00 00 00 00 00 00 00 00  ..Z.............
  backtrace:
    [<ffffffff>] 0xffffffff
unreferenced object 0xddc18230 (size 8):
  comm "swapper", pid 1, jiffies 4294671231 (age 873.952s)
  hex dump (first 8 bytes):
    30 00 c1 dd 00 00 00 00                          0.......
  backtrace:
    [<ffffffff>] 0xffffffff
unreferenced object 0xddc18240 (size 8):
  comm "swapper", pid 1, jiffies 4294671231 (age 873.952s)
  hex dump (first 8 bytes):
    31 00 c1 dd 00 00 00 00                          1.......
  backtrace:
    [<ffffffff>] 0xffffffff
unreferenced object 0xddc18250 (size 8):
  comm "swapper", pid 1, jiffies 4294671231 (age 873.952s)
  hex dump (first 8 bytes):
    32 00 c1 dd 00 00 00 00                          2.......
  backtrace:
    [<ffffffff>] 0xffffffff
unreferenced object 0xddc18260 (size 8):
  comm "swapper", pid 1, jiffies 4294671231 (age 873.952s)
  hex dump (first 8 bytes):
    33 00 c1 dd 00 00 00 00                          3.......
  backtrace:
    [<ffffffff>] 0xffffffff
unreferenced object 0xddc18270 (size 8):
  comm "swapper", pid 1, jiffies 4294671231 (age 873.952s)
  hex dump (first 8 bytes):
    34 00 c1 dd 00 00 00 00                          4.......
  backtrace:
    [<ffffffff>] 0xffffffff
unreferenced object 0xddc18280 (size 8):
  comm "swapper", pid 1, jiffies 4294671231 (age 873.952s)
  hex dump (first 8 bytes):
    35 00 c1 dd 00 00 00 00                          5.......
  backtrace:
    [<ffffffff>] 0xffffffff
unreferenced object 0xddc18290 (size 8):
  comm "swapper", pid 1, jiffies 4294671231 (age 873.952s)
  hex dump (first 8 bytes):
    36 00 c1 dd 00 00 00 00                          6.......
  backtrace:
    [<ffffffff>] 0xffffffff
unreferenced object 0xddc182a0 (size 8):
  comm "swapper", pid 1, jiffies 4294671231 (age 873.952s)
  hex dump (first 8 bytes):
    37 00 c1 dd 00 00 00 00                          7.......
  backtrace:
    [<ffffffff>] 0xffffffff
unreferenced object 0xddc182b0 (size 8):
  comm "swapper", pid 1, jiffies 4294671231 (age 873.952s)
  hex dump (first 8 bytes):
    38 00 c1 dd 00 00 00 00                          8.......
  backtrace:
    [<ffffffff>] 0xffffffff
unreferenced object 0xddc182c0 (size 8):
  comm "swapper", pid 1, jiffies 4294671231 (age 873.952s)
  hex dump (first 8 bytes):
    39 00 c1 dd 00 00 00 00                          9.......
  backtrace:
    [<ffffffff>] 0xffffffff
unreferenced object 0xddc182d0 (size 8):
  comm "swapper", pid 1, jiffies 4294671231 (age 873.952s)
  hex dump (first 8 bytes):
    31 30 00 dd 00 00 00 00                          10......
  backtrace:
    [<ffffffff>] 0xffffffff

Re: Memory leaks from swapper, wpa_supplicant, glxgears

[Pavel Roskin]

On Fri, 2010-03-26 at 14:58 +0100, Daniele C. wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hello there,
> 
> I have enabled CONFIG_KMEMLEAK and I am finding some memory leakage
> apparently caused by "swapper" process; I have also had leaks from
> glxgears and wpa_supplicant, but they can be triggered only once (e.g.
> restarting wpa_supplicant does not trigger more leaks).
> 
> The swapper leaks seem to be an incremental decimal string, starting
> from "0" to "10", while the wpa_supplicant leaks were the AP ESSID
> (not in attached report).

The attachment is quite useless since it has no function names, only
numeric addresses that vary between systems.

The backtrace that only has 0xffffffff suggests that kmemleak is not
working properly on your system.

Please figure out how to use kmemleak first.

-- 
Regards,
Pavel Roskin