Bug 31175 - Incorrect scale lines in xload window
Summary: Incorrect scale lines in xload window
Status: RESOLVED INVALID
Alias: None
Product: xorg
Classification: Unclassified
Component: Lib/Xaw (show other bugs)
Version: git
Hardware: Other All
: medium normal
Assignee: Jeremy Huddleston Sequoia
QA Contact: Xorg Project Team
URL:
Whiteboard: 2011BRB_Reviewed
Keywords: patch
Depends on:
Blocks:
 
Reported: 2010-10-27 16:02 UTC by Cyril Brulebois
Modified: 2018-06-12 19:08 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Fix by Nikita V. Youshchenko (3.47 KB, patch)
2010-10-27 16:02 UTC, Cyril Brulebois
no flags Details | Splinter Review

Description Cyril Brulebois 2010-10-27 16:02:34 UTC
Created attachment 39823 [details] [review]
Fix by Nikita V. Youshchenko

From: <http://bugs.debian.org/167448>
Reported-by: "Nikita V. Youshchenko" <yoush@cs.msu.su>

Excerpt:

Recently I tried to run xload on a high loaded server (load was more
than 10), and discovered that if window size is rather small, scale
lines are drawn incorrectly (upper than needed).

This is caused by a bug in Xaw/StripChart.c.
It draws lines with fixed integer steps. Than means that if window
height is 39 pixels, and 10 lines should be drawn to split view into 11
equal parts, lines will be drawn at 3, 6, 9, ,.., 30. So the bottom part
height will be 9 pixels while other parts height will be 2 pixels.

We've been shipping a patch for a while now; submitting upstream for reviewing/merging…
Comment 1 Jesse Adkins 2010-10-31 12:45:18 UTC
Can you send this to xorg-devel@lists.freedesktop.org for review if you haven't already?
Comment 2 Jeremy Huddleston Sequoia 2011-10-05 09:04:30 UTC
low hanging fruit.  I'll review this one.
Comment 3 Adam Jackson 2018-06-12 19:08:08 UTC
Mass closure: This bug has been untouched for more than six years, and is not
obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases.


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.