mailing-list for TeXmacs Users

[Massimiliano Gubinelli <address@hidden>]

Maybe, something is going wrong in your runloop. If you look into 
Plusings/Qt/qt_gui.cpp you see that we use a QTimer to fire an update 
procedure which runs TeXmacs internal update routines (reading input events 
from a secondary queue, performing changes and updating the window graphic 
surfaces). Maybe something is changed in the version of Qt5 which you have 
and this makes this bug appear, it does not seems to me I have seen it on my 
Mac (with Qt4). If you want to try to debug you can see wether the update 
function is run too often and why. Usually the algorithm make sure that, 
unless there is input to handle, the update function is called with 
reasonable timeout (there are delayed events which are produced internally in 
TeXMacs which have to be handled anyway, like the update of the footer bar).

hth,
max


> On 28. Jul 2020, at 15:01, Sebastian Miele <address@hidden> wrote:
> 
> I am running a TeXmacs from the current master branch of
> github:texmacs/texmacs. I am on Arch Linux.
> 
> Under some circumstances, TeXmacs uses 100% CPU of one processor, even
> if none of its windows is visible, and (as far as I understand) should
> have nothing to do. I tried to find a recipe to reliably reproduce that
> behaviour, but failed until now. When it happens, it seems to not hurt
> functionality/reactivity. When the issue arises, it seems to persist
> until I quit TeXmacs.
> 
> Is this issue already known?