[texworks] CPU resources

Henrik Skov Midtiby henrikmidtiby at gmail.com
Sun Feb 6 10:12:01 CET 2011


An earlier version of the autocomplete.js script could enter an
infinite loop, if it was activated with no words in front of the
The problem was fixed 31 of january with the new version uploaded to [1]


[1] http://code.google.com/p/texworks/issues/detail?id=261

On 6 February 2011 02:51, Paul A Norman <paul.a.norman at gmail.com> wrote:
> Hi,
> Still had this happening with Tw from time to time - I have no idea
> what condition causes it - is there anything I can look up - a log or
> anything?
> After you quit Tw - the laptop fan still running hot, and CPU usage high.
> Tw has disappeared from view - looks like it has shut down.
> Tw does not show in Task Manager / Applications list, but does  in
> Task Manager / Processes - looking like it is utilising almost all of
> half a duel core processor..
> Has to be explicitly killed or it looks like it will hang around until
> the machine is rebooted or shut down, otherwise when this happens, it
> never seems to disappear from Task Manager / Processes by its self.
> I'm running ver 729 (just reinstalled it from
> TeXworks-w32-v0.3r729-build1.zip, to be sure) but it is misreporting
> as version 728
> ----- configuration info -----
> TeXworks version : 0.3r728 (MinGWcross)
> Install location : D:/latexportable/LaTexUtils/TeXWorks/texworks/TeXworks.exe
> Library path     : D:/latexportable/LaTexUtils/TeXWorks/texworks/config\
> pdfTeX location  : D:/LaTeXPortable/LatexUtils/MiTeX 2.8.3541
> Portabe/miktex/bin/pdftex.exe
> Operating system : Windows XP Professional Service Pack 3
> Qt4 version      : 4.7.1 (build) / 4.7.1 (runtime)
> Paul
> On 16 January 2011 15:40, Paul A Norman <paul.a.norman at gmail.com> wrote:
>> Hi,
>> I realise this can probably not be directly answered but write it up in
>> case any one has more information on it towards future resolution..
>> I was running Tw 0.3, rev 726, (Xp Pro SP3, dual core), and noticed that the
>> fan on the lap top was running 'hot'.
>> So explored to see what was using the CPU.
>> Tw was the culprit.
>> Yet all I was currently doing was just editing.
>> So opened a new blank Tw document and closed the Tw document I had been
>> editing.
>> Still Tw was churning through the CPU.
>> So I closed it (the last Tw window), and still it showed as an
>> active process churning through the CPU around 50% (half a dual core).
>> I extinguished the Tw process, and the CPU returned to normal, and the fan
>> stopped racing.
>> Paul

More information about the texworks mailing list