@hdave, Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible? * If so, what specific steps should we take to recreate this bug? This will help us to find and resolve the problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to geoclue in Ubuntu. https://bugs.launchpad.net/bugs/951496 Title: indicator-datetime-session severely leaks memory Status in The Date and Time Indicator: Invalid Status in “geoclue” package in Ubuntu: Fix Released Status in “indicator-datetime” package in Ubuntu: Incomplete Bug description: After the most recent update to 0.3.91-0ubuntu1, indicator-datetime-session's memory increases at a rate of ~5MB/s, rendering my system unusable in a couple of minutes. Any advice on how to debug this issue? The service is always respawned after I kill it, making it impossible to directly run it in a terminal -- is there a way to prevent that? The issue persists even if I switch off the date display in the indicator bar. If I do an strace to the running process, the following seems to be repeated in an infinite loop: open("/usr/share/zoneinfo/Europe/Paris", O_RDONLY) = 14 fstat(14, {st_mode=S_IFREG|0644, st_size=2945, ...}) = 0 mmap(NULL, 2945, PROT_READ, MAP_PRIVATE, 14, 0) = 0x7fd1a6bd9000 close(14) = 0 munmap(0x7fd1a6bd9000, 2945) = 0 open("/usr/share/zoneinfo/UTC", O_RDONLY) = 14 fstat(14, {st_mode=S_IFREG|0644, st_size=118, ...}) = 0 mmap(NULL, 118, PROT_READ, MAP_PRIVATE, 14, 0) = 0x7fd1a6bd9000 close(14) = 0 munmap(0x7fd1a6bd9000, 118) = 0 open("/usr/share/zoneinfo/Europe/Paris", O_RDONLY) = 14 fstat(14, {st_mode=S_IFREG|0644, st_size=2945, ...}) = 0 mmap(NULL, 2945, PROT_READ, MAP_PRIVATE, 14, 0) = 0x7fd1a6bd9000 close(14) = 0 munmap(0x7fd1a6bd9000, 2945) = 0 open("/usr/share/zoneinfo/America/Los_Angeles", O_RDONLY) = 15 fstat(15, {st_mode=S_IFREG|0644, st_size=2819, ...}) = 0 mmap(NULL, 2819, PROT_READ, MAP_PRIVATE, 15, 0) = 0x7fd1a6bd9000 close(15) = 0 munmap(0x7fd1a6bd9000, 2819) = 0 poll([{fd=3, events=POLLIN}, {fd=10, events=POLLIN}, {fd=12, events=POLLIN}, {fd=11, events=POLLIN}], 4, 0) = 2 ([{fd=3, revents=POLLIN}, {fd=11, revents=POLLIN}]) read(3, "\1\0\0\0\0\0\0\0", 16) = 8 sendmsg(11, {msg_name(0)=NULL, msg_iov(2)=[{"l\1\0\1\0\0\0\0000\r\4\0\225\0\0\0\1\1o\0(\0\0\0/org/fre"..., 168}, {"", 0}], msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 168 sendmsg(11, {msg_name(0)=NULL, msg_iov(2)=[{"l\1\0\1\0\0\0\0001\r\4\0\233\0\0\0\1\1o\0(\0\0\0/org/fre"..., 176}, {"", 0}], msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 176 write(3, "\1\0\0\0\0\0\0\0", 8) = 8 recvmsg(11, {msg_name(0)=NULL, msg_iov(1)=[{"l\4\1\1\35\0\0\0F\336b\1\247\0\0\0\1\1o\0(\0\0\0/org/fre"..., 2048}], msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 325 write(3, "\1\0\0\0\0\0\0\0", 8) = 8 write(3, "\1\0\0\0\0\0\0\0", 8) = 8 write(3, "\1\0\0\0\0\0\0\0", 8) = 8 recvmsg(11, {msg_name(0)=NULL, msg_iov(1)=[{"l\3\1\1:\0\0\0I\336b\1w\0\0\0\6\1s\0\6\0\0\0:1.354\0\0"..., 2048}], msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 194 write(3, "\1\0\0\0\0\0\0\0", 8) = 8 recvmsg(11, 0x7fff9e33d3d0, MSG_CMSG_CLOEXEC) = -1 EAGAIN (Resource temporarily unavailable) write(3, "\1\0\0\0\0\0\0\0", 8) = 8 poll([{fd=3, events=POLLIN}, {fd=10, events=POLLIN}, {fd=12, events=POLLIN}, {fd=11, events=POLLIN}], 4, 0) = 1 ([{fd=3, revents=POLLIN}]) read(3, "\6\0\0\0\0\0\0\0", 16) = 8 poll([{fd=3, events=POLLIN}, {fd=10, events=POLLIN}, {fd=12, events=POLLIN}, {fd=11, events=POLLIN}], 4, 0) = 0 (Timeout) read(3, 0x7fff9e33d5d0, 16) = -1 EAGAIN (Resource temporarily unavailable) write(2, "\nIndicator-Datetime-WARNING **: "..., 117) = 117 poll([{fd=3, events=POLLIN}, {fd=10, events=POLLIN}, {fd=12, events=POLLIN}, {fd=11, events=POLLIN}], 4, 0) = 0 (Timeout) read(3, 0x7fff9e33d5d0, 16) = -1 EAGAIN (Resource temporarily unavailable) write(2, "\nIndicator-Datetime-WARNING **: "..., 72) = 72 sendmsg(11, {msg_name(0)=NULL, msg_iov(2)=[{"l\1\0\1\0\0\0\0002\r\4\0\215\0\0\0\1\1o\0(\0\0\0/org/fre"..., 160}, {"", 0}], msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 160 write(8, "\1\0\0\0\0\0\0\0", 8) = 8 write(7, "\1\0\0\0\0\0\0\0", 8) = 8 futex(0x7fd1a000b780, FUTEX_WAKE_PRIVATE, 1) = 1 futex(0x7fd1a000b2e0, FUTEX_WAKE_PRIVATE, 1) = 1 futex(0x20e7e00, FUTEX_WAKE_PRIVATE, 1) = 1 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: indicator-datetime 0.3.91-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 CheckboxSubmission: 476acdb7217a83354f628beaa5c14f06 CheckboxSystem: daed2f3d6643b4a84b4520a2427f8c2b Date: Sat Mar 10 13:29:07 2012 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100114) ProcEnviron: TERM=xterm LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: indicator-datetime UpgradeStatus: Upgraded to precise on 2012-01-20 (49 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/951496/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
