The amount of 'Total sent' data wraps around at 4GB

Bug #373243 reported by misiu_mp on 2009-05-07
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Gnome System Monitor
Unknown
Low
linux (Ubuntu)
Low
Unassigned

Bug Description

Binary package hint: gnome-system-monitor

This is related to the closed bug #284423 (the reporting user didnt follow up the report).

It looks like 'Total sent' (or received) amount of bytes is kept in a 32bit variable and is wrapped around each ~4GB sent (2^32 bytes).
You will never see total sent larger than 4GB. When the wrap happens you can see the transfer rate graph go to zero for a moment. Caused probably by using the wrapped variable in calculating speed (prev = 4GB, new =0 => speed negative).
Changing the counter to 64bits should be a temporary fix. In the long run some kind of bignum is needed (or decrease resolution and count the amount of kB transmitted, or MB, GB).
Leaving it as is makes the counter quite useless especially as you can achieve gigabit speeds on networks today it deasnt take long to exceed the 4 GB transmitted data.

This is all speculations as I didn't look at the source, but it seems quite clear to me.

Happens in all versions of gnome-system-monitor (including the one in 9.04).

Pedro Villavicencio (pedro) wrote :

Haven't found anything upstream related to this, could you please send it directly at bugzilla.gnome.org since you're getting the issue? for forwarding instructions please have a look to https://wiki.ubuntu.com/Bugs/Upstream/GNOME ; Thanks in advance.

Changed in gnome-system-monitor (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → Low
Changed in gnome-system-monitor:
status: Unknown → New
Pedro Villavicencio (pedro) wrote :

Thanks for sent it upstream.

Changed in gnome-system-monitor (Ubuntu):
status: New → Triaged
misiu_mp (misiu-mp) wrote :

They are not too keen on taking it though. Seems there is no bug tracker for gnome-system-monitor.

Sebastien Bacher (seb128) wrote :

upstream bug comment

"That's a linux issue on 32bits arch.
Counter are 64bits for performance."

affects: gnome-system-monitor (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
assignee: Ubuntu Desktop Bugs (desktop-bugs) → nobody
status: Triaged → New
Changed in gnome-system-monitor:
status: New → Invalid
kernel-janitor (kernel-janitor) wrote :

Hi misiu-mp,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/releases/ . Please then run following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux-image-`uname -r` 373243

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
misiu_mp (misiu-mp) wrote :

Package was wrongly chosen as linux, trigging kernel log request which seems unrelated to this bug. Changed to gnome-system-monitor

affects: linux (Ubuntu) → gnome-system-monitor (Ubuntu)
Sebastien Bacher (seb128) wrote :

the bug was not wrongly assigned that's a linux issue as stated on the GNOME bug

affects: gnome-system-monitor (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: Incomplete → New
misiu_mp (misiu-mp) wrote :

This is madness. This doesnt have anything to do with linux and those at gnome-bugs dont really care for this ...
The only way this could remotely be related to the kernel is that runnig a 64 bit kernel would allow to run a 64bit version of the program and the counter warp around would disappear. This is not the way to approach this problem though, as 32bit systems are still (probably) used by the majority of users and they have the right to correct counter as well.

Vikram Dhillon (dhillon-v10) wrote :

Unfortunately it seems this bug is still an issue. Can you confirm this issue exists with the most recent Lucid Lynx 10.04 release - http://cdimage.ubuntu.com/releases/lucid/alpha-2/. If the issue remains in Lucid, please test the latest 2.6.32 upstream kernel build - https://wiki.ubuntu.com/KernelMainlineBuilds . Let us know your results. Thanks.

Changed in linux (Ubuntu):
status: New → Incomplete
Changed in gnome-system-monitor:
importance: Unknown → Low
status: Invalid → Unknown
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.