[texworks] CPU 100% when viewing pdf

Stefan Löffler st.loeffler at gmail.com
Mon Jun 28 07:22:54 CEST 2010


Am 2010-06-27 21:39, schrieb kap4lin:
> On Fri, Jun 25, 2010 at 10:04 PM, kap4lin <kap4lin at gmail.com> wrote:
>> I updated TeXworks to the current r663 version and "hell broke loose."
>> The CPU usage is 100% when a pdf file is opened. And Tw just stops
>> working. I have to kill the process. But no problems when just a tex
>> file is opened. Essentially, it is unusable now!
> [...]
>> I understand this is very minimal info to debug; so let me know, what
>> other info I can provide. The system is a KDE 3.5.4 RedHat 5.5.
> Hmm no response... I guess this is an unfamiliar situation to everyone!

Indeed it is... But you're right, this should be resolved somehow.
Unfortunately I don't know enough about your build process, so I'm left
with fairly general questions to get to the bottom of this:

 * Does this happen with all pdfs, even simple "Hello World" ones?
 * Does this happen if you start Tw in "pdf mode" (i.e., by running
`texworks myfile.pdf` to avoid loading any TeX window)?
 * What version did you upgrade from? (I know that you probably won't
know, but just to get an idea; do you update daily, weekly, monthly, or
have you been working for the last half year without update?)
 * Did you change anything else? (E.g., upgrade your operating system,
rebuild (one of) the libraries, etc.)

Somehow, this all sounds like a poppler issue to me as Tw doesn't do
much for the rendering of pdfs itself. But AFAIK there have been no
changes to that lately. The only thing that did change (but shouldn't
cause such severe problems, at least at first glance) was the way pdfs
were attached to texs (so they close together, for example). So:

 * If you have an idea of the last revision that worked, could you
backdate your working copy to that (by `svn update -r <REVNO>` where you
fill in "<REVNO>") and see if it still works as expected? If it does,
could you narrow down the revision that introduced the problem?

> So, here is another idea: Is it possible to create a static build?

In principle, yes. Though I'm not sure how exactly this should help. But
of course you'd need to build all libraries again statically. I've never
done this myself, except for the windows cross builds I posted recently,
and most of that is based on the MinGW-cross-env project
(http://www.nongnu.org/mingw-cross-env/). You can take a look at my
scripts at https://code.launchpad.net/~texworks/packaging/win32 if you
want, though.

> I had grown too used the synctex feature and now it is difficult to
> get back to Kile + Kdvi setup.

Let's hope you don't have to :). No, seriously, this problem should be


More information about the texworks mailing list