I plan to upload an NMU of this package to the DELAYED queue today, with
the attached differences.
diff -u hardware-monitor-1.2.1/config.guess hardware-monitor-1.2.1/config.guess
--- hardware-monitor-1.2.1/config.guess
+++ hardware-monitor-1.2.1/config.guess
@@ -1,9 +1,10 @@
#! /bin/sh
# Attempt
According to the associated Ubuntu bug report, hardware-monitor 1.3
fixes this problem.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Karl Chen <[EMAIL PROTECTED]> writes:
> Now that I've gotten this far I figure it should be easy to
> reproduce :) Just play back the values to a CurveView monitor.
>
> It looks to me like a chain of bugs triggered by an unlikely
> scenario: 1. The value shouldn't be 2e19 in the first place (is
Just to confirm this bug - h-m just ate 2Gb RAM and almost made my
machine unusable. Symptoms similar - sustained 740KB/s over a longer
period of time.
Hope you can find this.
/Mikael
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTEC
I've finally narrowed down the source of the bug where
hardware-monitor uses 2GB of RAM and 100% CPU, and has to be
killed.
The backtrace always showed it to be in
line->property_fill_color_rgba() = color;
in Curve::draw(), which didn't make any sense because
line->points() was never set to
On Mon, Feb 27, 2006 at 10:31:16PM -0800, Karl Chen wrote:
> Package: hardware-monitor
> Version: 1.2.1-3+b1
> Followup-For: Bug #330482
>
>
> This has been bothering me for a long time and I finally found a way to
> reliably reproduce it. While showing the ethernet ba
Package: hardware-monitor
Version: 1.2.1-3+b1
Followup-For: Bug #330482
This has been bothering me for a long time and I finally found a way to
reliably reproduce it. While showing the ethernet bandwidth, if I sustain
high network bandwidth for a couple minutes, it'll happen: hardware-mo
Package: hardware-monitor
Version: 1.2.1-2
Severity: normal
hardware-monitor eats up memory quickly and is killed by the out of
memory kill procedure (oom) after utilizing the complete memory and swap
area.
I have no idea what exactly caused the memory problem. At the beginning,
hardware-moni
8 matches
Mail list logo
