Bug#527992: Program abruptly closes without warning when network bit rate too high (>400MiB/s)

[Tom]

Package: gnome-system-monitor
Version: 2.22.3-1

Note: I'm actually not sure the exact version number I saw this on and don't
have access to the computer I was using before.  I saw issue on the amd64
version of gnome-system-monitor that came with Debian 5.0 / Lenny, possibly
with some auto-updates applied.

It is, for me at least, easily reproducible.  If a network interface exceeds
about 400 MiB/s, gnome-system-monitor will just close without giving any
notice.  If the network bit rate was > 400 MiB/s at the time
gnome-system-monitor started, it took less than two seconds before it
closed.  I verified if I lowered my rate to a bit under 400 MiB/s things
worked fine.

I realize that bit rate is high enough it may seem too difficult to
test/verify.  With a fast PC and 4 gigabit ports, my setup may be useful to
reproduce.  It may be quicker though to just make some test code that when
activated does something such as multiplying the bit rate when
gnome-system-monitor first reads it.

My setup made use of the Kernel version Click modular router
(http://read.cs.ucla.edu/click/), 4 Intel gigabit Ethernet ports (integrated
on the mainboard, but that probably doesn't matter), and the Linux Ethernet
bonding driver.  Essentially my Click config was the same as the example
udpgen.click on the website with the PollDevice() line removed and the
UDPGen parameters updated to generate large packets at 4 gb/s.