Control: tags -1 pending
On Mon, 6 Nov 2017 09:58:29 -0500 Doug Torrance wrote:
> Wonderful, thank you! I've submitted the patch upstream and hope to
> release a new Debian version soon.
FYI, a new upstream version containing this patch (2.51) has been released:
http://www.dockapps.net/wmbattery
On 11/06/2017 09:32 AM, David Johnson wrote:
FYI: I've been running with this patch applied for over a week, no
issues seen. Please apply unless there is an alternative.
David Johnson writes:
I've concluded libupower-glib is just super leaky. The below patch
moves the upower API calls into
FYI: I've been running with this patch applied for over a week, no
issues seen. Please apply unless there is an alternative.
David Johnson writes:
>
> I've concluded libupower-glib is just super leaky. The below patch
> moves the upower API calls into a child process that doesn't exist for
>
I've concluded libupower-glib is just super leaky. The below patch
moves the upower API calls into a child process that doesn't exist for
long to keep the leaks out of the main process.
Tested against stretch versions, looks good.
--- wmbattery-2.50.orig/upower.c2015-08-30 19:58:13.
With the patch provided to remove the extra up_client_new() calls, I
still see these 3 leaks from within up_client_get_devices().
Neither g_ptr_array_free() or g_ptr_array_unref() are cleaning them
up.
I'm assuming a more comprehensive fix would be to remove
up_client_get_devices() from upower_r
Doug,
When I first filed this bug I did some digging with valgrind trying to
find the leaks.
I found several issues with the upower module (the older methonds were
less leaky). valgrind found lots of leaks, but they were hard to
trace, except that most/all were in the upower area. I suspect th
On 10/19/2017 12:43 PM, bw wrote:
On Thu, 19 Oct 2017, Tim Connors wrote:
Package: wmbattery
Version: 2.50-1+b1
Followup-For: Bug #816872
Dear Maintainer,
Memory bug is still present, nice app though overall, thanks.
Hi, this just killed my system (13GB RSS, 20GB VMM).
Oct 19 22:46:35 dir
> Package: wmbattery
> Version: 2.50-1+b1
> Followup-For: Bug #816872
>
> Dear Maintainer,
>
> Memory bug is still present, nice app though overall, thanks.
Hi, this just killed my system (13GB RSS, 20GB VMM).
Oct 19 22:46:35 dirac kernel: [163443.300793] Killed process 12027
(wmbattery) total-vm:
Package: wmbattery
Version: 2.50-1+b1
Followup-For: Bug #816872
Dear Maintainer,
Memory bug is still present, nice app though overall, thanks.
-- System Information:
Debian Release: 9.1
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-3-amd64 (
Control: forwarded -1 wmaker-...@lists.windowmaker.org
On 03/05/2016 10:24 PM, Dave Johnson wrote:
Package: wmbattery
Version: 2.45-2
Severity: important
Dear Maintainer,
wmbattery appears to have a memory leak. When invoked with "wmbattery -w 2" it
is leaking approx 350KB/minute on my syste
Package: wmbattery
Version: 2.45-2
Severity: important
Dear Maintainer,
wmbattery appears to have a memory leak. When invoked with "wmbattery -w 2" it
is leaking approx 350KB/minute on my system. Eventually it runs out of memory
and is killed by kernel.
$ while sleep 300; do ps u $(pidof wm
11 matches
Mail list logo
