First login?
Lost password?
 
 
 
mailing-list for TeXmacs Users

Text archives Help


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 11:05:20 -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 25/11/10 10:54, Gubinelli Massimiliano wrote:

Thanks for all these reports.
As pointed out by Sam, this bug is mostly probably linked with texmacs behavior under repainting. The current Qt solution (which is different from the X11 one due to limitations in the API) is to stop typesetting and repainting after a fixed amount of time and retry later to finish the work. This to allow user input and to avoid aving the GUI blocked while typesetting and repainting. Unfortunately I cannot reproduce the bug on my Mac and this make less easy for me to provide a reliable fix. I hope to be able to fix this issue soon.

Perhaps the amount of time could be increased or configurable in the mean time. Reasonably the likelihood of the bug to occur seems to relate to CPU load, which might help demonstrate the bug if some heavy task could run.

Although I've had the problem on my 500MHz netbook, I hadn't noticed the problem occur on my 2 core 2.6GHz laptop until I added the new low-latency patches everyone is talking about which allocates CPU resources into CPU groups - thus I think the texmacs group perhaps consumed it's resources too soon and some were given over to virtual machines I'm hosting - which may not have occurred if CPU were allocated on a per-process basis.

Sam
--


Archive powered by MHonArc 2.6.19.

Top of page