Skip to Content.
Sympa Menu

texmacs-users - Re: [TeXmacs] TeXmacs 1.0.7.8 refresh

Subject: mailing-list for TeXmacs Users

List archive

Re: [TeXmacs] TeXmacs 1.0.7.8 refresh


Chronological Thread 
  • From: "Sam Liddicott" <address@hidden>
  • To: address@hidden
  • Subject: Re: [TeXmacs] TeXmacs 1.0.7.8 refresh
  • Date: Thu, 25 Nov 2010 10:46:47 -0000
  • Envelope-to:
  • Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwCAMAAABg3Am1AAAAAXNSR0IArs4c6QAAADxQTFRF NTdQY2Z/i286eHFugnNXoJBwm5GCs5VeoqO0ua+fwLCQ4c2q19C81NDF4eLr/unQ/PTf/fXW+/rq /f/7XKo76wAAAAlwSFlzAAALEwAACxMBAJqcGAAAAi9JREFUSMetloGSqyAMRVsFNAQkxP//15cE 62rFdt/MZqbTVu/hBhLEx/qf8fgDIAN455wHyPk7wCIe9nA+fwGSH87hgD8AHPfRpy2GwdMtcBh+ mg4Ech9Ih+RNixJKDLEL0GF8VLkSojePHrDlryNijbFW8zBg8PUKbBOI6D1WCV5Rf2DzxCtgBlMs tRRVW5LyVW3ew1TfAZZ6RcQicpb4yZmaC74DJADK6BdATOrUAbJzsZie+K22ZnEBknNYysvhVH6u 1X8CqAe4DuANoPoOrAbsHXUARJ5knc5z4EyyTnHoAqj7xvkYIdk65AwhyEZKMusOIDV2QQQaCnDQ gBiDR3RdIEb5CBESt2wgQJI0Yx/Agphg1MgNsD+QkszM9wHVPx/PeQOW+fmcR9DF8+4CyCJhCuP8 fDzmBbLqs8JzMODqYNfDvKhoGYM2lDosy5jlRozccRAgrPM8iygQS3Mv87IugUgKlC7NZ6liuy4r uresVq5QuQAr09ZKEga8OkluyKXeQ6Bs3SrtqgC1pWLNqAfwDhBnB+sK8OrVL4D4h1B4zWPWhJhu gPUHKA5EwSMYUMsdQK+UKDhIOTSHeg+8HCoTOGtB/gwcl4mSdGybwXegPWhM/RHYKwchkckhUNMX 6j7ueQNScLbZZOPRxaADyO2UQCJpl7wbnE6gQ+ksWjpngxOwF1tF5ecP3R6KB+AQxPfHLncQ+nKw 06fhu68OTIfJ869eTtg22l+9zfwDK3mKl5BFHMYAAAAASUVORK5CYII=


On 24/11/10 15:26, Alvaro Tejero Cantero wrote:
TeXmacs 1.0.7.8 on Ubuntu 10.04 64 bit compiled with QT support enters
a refresh loop in my system whereby about 3 lines are constantly
visible, another 1-3 keep appearing-disappearing and the rest is
blank.

This also happens when visiting the documentation, so anybody can
check (it is not document-dependent).


I noticed today that a paint loop leaves the CPU load very high.

Observation also leads me to say that I think the processing of a paint message will quit after certain time has been taken and paint the rest later.

If painting takes too long, then texmacs will get into a loop (perhaps qt doesn't easily report that a smaller region needs painting, or perhaps texmacs can't take advantage of this).

I had a case today where the problem did not go away by switching focus or covering the window, and even other texmacs windows which had painted fine (and hadn't been scrolled) couldn't paint.

The solution was to minimize them till the load went low, and then when I restored the stuck window it could paint.

I wonder if the paint used up CPU share to the degree that it could never get enough CPU to finish painting and so got stuck in a loop of always trying to paint.

Just a guess.

Sam

-á.


--
[FSF Associate Member #2325] <http://www.fsf.org/register_form?referrer=2325>

<http://www.openrightsgroup.org/>



Archive powered by MHonArc 2.6.19.

Top of Page