I ran into this recently when I switched to a new 2560x1600 monitor. If I run xload with a window that's 2048 or fewer pixels wide, it works correctly. If the window size is more than 2048 pixels, it works correctly until 2048 data points have been plotted. Once it gets past 2048 plotted data points, it either crashes with a segmentation fault or misbehaves in some other way. In various circumstances, I've seen the window either stop updating or go blank. To reproduce: xload -geom 2050x200 -update 1 and wait about 34 minutes until the graph exceeds 2048 columns. Depending on the window manager, you might need a large X display to do this. I've seen this on Ubuntu 14.04 and 16.04. As a workaround, I'm running xload with width of 2048 pixels -- but if I maximize my xload window, it immediately crashes.
And here's the problem: ftp://ftp.x.org/pub/xorg/individual/lib/libXaw-1.0.13.tar.gz libXaw-1.0.13/include/X11/Xaw/StripCharP.h, line 74 double valuedata[2048]; /* record of data points */ Increasing the size would be a quick fix. Dynamic allocation would be another (but the size would need to increase if the window is resized).
Thanks for the report - patch submitted for code review: https://patchwork.freedesktop.org/patch/212798/ I wasn't sure if the size of valuedata could be changed without breaking the ABI, since it's embedded in the class structure, so I just added bounds checks to keep us from exceeding it. If you need more than 2048 points of load average data, you probably want a better monitoring tool than xload anyway.
https://cgit.freedesktop.org/xorg/lib/libXaw/commit/?id=f5699b698d512bb1060ef53704595d6accf7eb19
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.