All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alberto José Rodríguez Rodríguez" <ajrodriguez@blulabs.es>
To: linux-bluetooth@vger.kernel.org
Subject: bluetoothd OOM
Date: Mon, 12 Mar 2012 12:37:17 +0100	[thread overview]
Message-ID: <1331552237.5372.10.camel@localhost> (raw)

I have one machine that send files to the devices that it detects
(pairing when requested by the target device). But recently it goes out
of memory, and if a launch bluetoothd by hand I see thousands of lines
like this:

..................
bluetoothd[3341]: src/device.c:device_create() Creating
device /org/bluez/3341/hci1/dev_E4_EC_10_CD_56_C2
bluetoothd[3341]: src/device.c:btd_device_ref() 0x234e5988: ref=1
bluetoothd[3341]: src/device.c:device_set_temporary() temporary 0
bluetoothd[3341]: src/device.c:device_probe_drivers() Probing drivers
for E4:EC:10:CD:56:C2
bluetoothd[3341]: src/device.c:device_create() Creating
device /org/bluez/3341/hci1/dev_FC_A1_3E_11_6D_81
bluetoothd[3341]: src/device.c:btd_device_ref() 0x234eb4c8: ref=1
bluetoothd[3341]: src/device.c:device_set_temporary() temporary 0
bluetoothd[3341]: src/device.c:device_probe_drivers() Probing drivers
for FC:A1:3E:11:6D:81
bluetoothd[3341]: src/device.c:device_create() Creating
device /org/bluez/3341/hci1/dev_E0_A6_70_49_6E_6A
bluetoothd[3341]: src/device.c:btd_device_ref() 0x234ee6d8: ref=1
bluetoothd[3341]: src/device.c:device_set_temporary() temporary 0
bluetoothd[3341]: src/device.c:device_probe_drivers() Probing drivers
for E0:A6:70:49:6E:6A
bluetoothd[3341]: src/device.c:device_create() Creating
device /org/bluez/3341/hci1/dev_00_26_CC_6B_F8_0A
....................

It seems to remember all the devices that are paired once. How I can
make him clean them?

Thanks in advance


                 reply	other threads:[~2012-03-12 11:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1331552237.5372.10.camel@localhost \
    --to=ajrodriguez@blulabs.es \
    --cc=linux-bluetooth@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.