lyx 1.6.x impossibly slow

Bug #353449 reported by Christopher Barrington-Leigh
76
This bug affects 13 people
Affects Status Importance Assigned to Milestone
lyx (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: lyx

I am using lyx 1.6.1 on Ubuntu 8.10. This program used to be my do-everything software, but it has become unusably slow. That is, keystrokes are even delayed in displaying when I type. The rest of the system is fine, and LyX didn't used to have such a problem. I'm not sure where to start in debugging this.

 apt-cache policy lyx
lyx:
  Installed: 1.6.1-1~intrepid1
  Candidate: 1.6.1-1
  Version table:
     1.6.1-1 0
        500 http://ca.archive.ubuntu.com jaunty/universe Packages
 *** 1.6.1-1~intrepid1 0
        100 /var/lib/dpkg/status

lsb_release -rd
Description: Ubuntu 8.10
Release: 8.10

Revision history for this message
Christopher Barrington-Leigh (cpbl) wrote :

The problem exists for me under both metacity and the compizfancything.

Revision history for this message
Johannes Hessellund (osos) wrote :

I just installed Jaunty last night, and as part of it, LyX 1.6.2 from the repos.

LyX seems incredible sluggish while scrolling.
While scrolling in LyX, xorg uses 99% cpu !

This might be related!

I had no troubles on Intrepid!

summary: - lyx 1.6.1 impossibly slow on a fast Ubuntu 8.10
+ lyx 1.6.x impossibly slow
Revision history for this message
Chris Dickson (whiskychris) wrote :

I am using lyx 1.6.2 on Jaunty and have extreme typing delay when working on my large project report (currently ~40 pages long). It's straightforward to type more than four or five words ahead of what is displayed on screen and this causes lyx to grey out while it catches up. This is extremely irritating but not critical as I've not lost any data (luckily!)

I've just tested lyx when typing in a fresh document and it doesn't have the same problems, so perhaps there's something confusing it when editing a large document. Does anyone else notice this effect more or less when editing different sizes of files?

Changed in lyx (Ubuntu):
status: New → Confirmed
Revision history for this message
Johannes Hessellund (osos) wrote :

I found that the slowdown was actually my xorg driver.

I have a radeon7500 using the radeon driver. Switching to XAA acceleration fixed this.
Now scrolling and typing is just like Intrepid.

See bug #363238.

Revision history for this message
Kosumo (mas-kosumo) wrote :

I found the same condition. I am using lyx 1.6.2 on Ubuntu Jaunty. My graphic card is Intel GMA X3100 graphics. Anyone find the solution?

Revision history for this message
wch (winston-stdout) wrote :

Same issue with Intel 945GME on a Dell Mini 9.

Revision history for this message
wch (winston-stdout) wrote :

I found that upgrading to QT 4.5.1 (from Karmic alpha) improved performance a lot. Scrolling isn't instantaneous on my computer, but it is much, much better, and it may be because my computer is an underpowered netbook.

Instructions here:
http://<email address hidden>/msg74482.html

Revision history for this message
arno_b (arno.b) wrote :

I have this problem when I use an external screen (22'') with my netbook (samsung N510). I think that the graphical card has some difficulties to manage lyx with a big screen.

Revision history for this message
arno_b (arno.b) wrote :

oops.. I use karmic

Revision history for this message
Jens Janssen (jayjay) wrote :

I use Ubuntu 10.10 but the problem is still persistent.

tags: added: lyx scrolling slow sluggish typing
Revision history for this message
Kosumo (mas-kosumo) wrote :

The easiest way to deal with this problem is to divide your work into several parts. For example if you write a thesis, you can divide your work into several chapters. You just create a master lyx document and you can put there only the title of all chapters. For the detail of each chapter you create separate lyx documents and insert each of them using Insert->File->Child Document. By using this way, even if you put your bibliography in the master document. You can still access the references from each child document. The only requirement is you must open you child document from the master.

Example of the structure of master document:

Title
Table of contents

Chapter 1 Introduction
Input: chapter1.lyx

Chapter 2 Literature Review
Input: chapter2.lyx

....

Bibliography

Revision history for this message
Jens Janssen (jayjay) wrote :

Kosumo, thank you for your detailed description.

But the overall speed is not a matter of key strokes. It is slow from the beginning (marking text, copy/paste, typing, scrolling...).

It feels like a remote desktop.

Revision history for this message
Kosumo (mas-kosumo) wrote :

@Jens, Yeah... that was exactly what I experienced in my computer last year. At the moment, I use Lyx 1.6.4 on Ubuntu 9.10 and I have no problem with it because mostly I only write around 20 or 30 pages per file.
I know it is annoying problem especially if you have a lot of pages to write or edit. Maybe you can try to open the Lyx application in KDE instead of GNOME or even try to downgrade to lower version of Lyx (maybe ver 1.5 or so).

Revision history for this message
LundLinux (andlund) wrote :

It persists in lyx 2.0.0. My solutions is to switch to console mode and back again, ctrl+alt+F1 and then ctrl+alt+F8(F7). Then the speed is great, for a while...;)

Revision history for this message
Donjan Rodic (bryonak) wrote :

Running on a machine with Ubuntu 10.10 64bit and Lyx 1.6.7 as well as 1.6.8.
Not sure if it's the same bug, but in my case, I isolated the problem to a simple procedure:
Close everything (best to reboot) and start up only your LyX file. Scrolling and writing should be fast even with big documents.
Hit the "View PDF" toolbar button to compile it. For me it opens up in Evince.
Now go back to LyX (alt+tab or click the window list), scrolling and writing suddenly becomes very slow.
Minimise the Evince window, then minimise and unminimise the the LyX window - everything is fast and smooth again.
It stays fast as long as the Evince window is minimised so far, will have to investigate further.

Very strange behaviour... this workaround behaviour works for me but I can't explain it. Hope it helps someone else...

Revision history for this message
Jean-Marc Lasgouttes (jmarc) wrote : Re: [Bug 353449] Re: lyx 1.6.x impossibly slow

Le 19 déc. 2010 à 23:32, Pavel Sanda a écrit :
Jean-Marc Lasgouttes wrote:
>> Running on a machine with Ubuntu 10.10 64bit and Lyx 1.6.7 as well as
>> 1.6.8.
>> Not sure if it's the same bug, but in my case, I isolated the problem to a
>> simple procedure:
>> Close everything (best to reboot) and start up only your LyX file.
>> Scrolling and writing should be fast even with big documents.
>> Hit the "View PDF" toolbar button to compile it. For me it opens up in
>> Evince.
>> Now go back to LyX (alt+tab or click the window list), scrolling and
>> writing suddenly becomes very slow.
>> Minimise the Evince window, then minimise and unminimise the the LyX window
>> - everything is fast and smooth again.
>> It stays fast as long as the Evince window is minimised so far, will have
>> to investigate further.
>>
>> Very strange behaviour... this workaround behaviour works for me but I
>> can't explain it. Hope it helps someone else...
>
> evince is not qt based, so i cant imagine what can cause such interference.
> do yo se some clipboard manager btw?

I don't, but I am not the author of the comment. I can ask, though.

Could there be some connection between evince and LyX (related to forward/backward search)?

JMarc

Revision history for this message
landroni (landroni) wrote :

https://bugs.launchpad.net/bugs/353449

On Mon, Dec 20, 2010 at 9:54 AM, Jean-Marc Lasgouttes
<email address hidden> wrote:
>> evince is not qt based, so i cant imagine what can cause such interference.
>> do yo se some clipboard manager btw?
>
> I don't, but I am not the author of the comment. I can ask, though.
>
> Could there be some connection between evince and LyX (related to forward/backward search)?
>
I don't think 1.6.7 provides this functionality, unless the user is
using some fancy config.

In any case, I have Xubuntu 10.04 on 64 bit with LyX 1.6.7, and I
cannot reproduce this. I've been using LyX and Evince for a long time
now, and I've never encountered anything similar.

Regards
Liviu

Revision history for this message
landroni (landroni) wrote :

On Mon, Dec 20, 2010 at 9:54 AM, Jean-Marc Lasgouttes
<email address hidden> wrote:
> Could there be some connection between evince and LyX (related to forward/backward search)?
>
I've been reading the descriptions in the bug report, and I'm
wondering if some of them are not related to the table painting issues
that were discussed some time ago on the list (tables are re-drawn on
each cursor movement). Another possibility is the slow-downs caused by
outline with a complicated document structure. But the one that you've
forwarded looks strange, indeed.

Regards
Liviu

Revision history for this message
landroni (landroni) wrote :

On Mon, Dec 20, 2010 at 2:34 PM, Pavel Sanda <email address hidden> wrote:
> Liviu Andronic wrote:
>> I don't think 1.6.7 provides this functionality, unless the user is
>> using some fancy config.
>
> but if he uses, then backward search using lyx pipes can be related,
> the pipe handling code is dark enough ;)
>
> anyway, the comment:
>
> "It persists in lyx 2.0.0. My solutions is to switch to console mode and back again,
> ctrl+alt+F1 and then ctrl+alt+F8(F7). Then the speed is great, for a while...;)"
>
> is even more weird workaround for the slowness bug. it could be that we are encoutering
> something even deeper than qt's - X related behaviour.
>
> it would be fantastic if anybody who is experiencing this bug can make some deeper
> profiling.
>
gdb or valgrind? Or some other technique?

Liviu

> pavel
>

--
Do you know how to read?
http://www.alienetworks.com/srtest.cfm
http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader
Do you know how to write?
http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail

Revision history for this message
Donjan Rodic (bryonak) wrote :

After compiling and running the latest LyX 2.0 RC1, the problem still persists. My minimise workaround got a bit more tedious (having to retry a few times).

The lag (with maxed out CPU usage) happens when both scrolling and writing (but not when opening menus) and depends on the window size. For tiny windows, it's nearly imperceptible, full screen windows are unusably slow. Thus it might have something to do with redrawing.
The maximum "lag free" (yet with 80%-100% CPU usage) size with Evince minimised is about 600x600, with Evince right besides LyX roughly 250x250.

My current paper is relatively straightforward: paragraphs with lots of math formulas. Every other document I tried exhibits the same behaviour.

However, after turning off Compiz, everything went smoothly, without a single lag.
Since I really don't want to miss Compiz' usability extensions, I hoped to find some config settings (direct output, syncing, ...) to improve the situation. Fiddling around in CCSM and nvidia-settings was fruitless so far.
Turning on Metacity's compositing feature (without Compiz) reintroduced the lag.

I tried recompiling with ./configure --enable-debug ... but what is supposed to be done then?

Currenly my best bet is using LyX in a 600x600 window and applying the minimise-Evince workaround, which isn't exactly enjoyable, but more acceptable than turning off Compiz.

Revision history for this message
Jean-Marc Lasgouttes (jmarc) wrote :

I would propose to recompile with --enable-build-type=prof, compile, and then run LyX under
a profiler like sysprof. This should show what is the process that uses all the time. If it turns out that it is X, then I am not sure how to proceed.

Revision history for this message
Donjan Rodic (bryonak) wrote :

In the meantime I've switched to a new machine (Core i) and Lyx 2.0.0 final on Debian.
CPU usage of one core (of four) still rockets up when scrolling/writing in a large LyX window, but it's smooth enough and works without big lags.

So for me this is "solved", I'm afraid I'm not going to debug my previous situation any further.
Thanks for your help so far!

Revision history for this message
Evan Langlois (uudruid74) wrote :

I just changed from the proprietary ATI driver to Radeon (as a result of switching to kernel 3.16) and this bug now affects me. I'm pretty sure its the driver. I'm also using compiz. Not sure why LyX is so slow when other apps aren't, but a multi-Ghz machine should be able to keep up with how fast I can type.

Isn't it funny how hardware is at a blazing speed, but the "useable" speed is roughly the same as a few decades ago. Infact, I think my Atari ST could open windows faster than my Ubuntu box.

Possible Workaround. If using Compiz, load ccsm and see if the Copy To Texture plugin is on. If so, see if turning it off helps. It seems to work for me. I'm wondering if LyX isn't reporting what part of the screen was damaged properly or something like that and its causing compiz to copy the whole window to the texture instead of just the damaged area. This would explain why a smaller window helps. I'm betting the bug only recently hit me either because the fglrx driver has a hardware speed-up for copy to texture or because I didn't have the Copy turned on before (I had to reconfigure a few things when I switched).

Do we have any authors that can look at the code or whatever library is being used?

Revision history for this message
Jean-Marc Lasgouttes (jmarc) wrote :

With my LyX developer hat on:

It is known indeed that LyX has problems with the way display is handled. Unfortunately,
nobody is has the right amount of knowledge and free time to fix that currently.

I would be interested to know what happens if you add to your preferences file (usually in the ~/.lyx directory) the
line:
  \use_qimage false

This will make LyX use a Pixmap (that lives in the display server) instead of an image which lives in main memory.

Revision history for this message
Evan Langlois (uudruid74) wrote :
Download full text (3.2 KiB)

This is incredibly weird.

I added the line to preferences ...

If I start with Copy To Textures off, its OK an I can turn Copy To
Preferences back on while Lyx is running and it looks like the preferences
line has fixed things. It looks very quick like this. I then turned Copy
To Texture back off, as it was when I started it. Its worse than ever! I
turn copy to texture back on, and its back to being slow (like before any
of this started). Turning off Copy to Texture fixes it again.

If I start with Copy to Textures on, it looks like the preferences change
has fixed it. I turn Copy To Textures off, and now its so slow that it
misses keystrokes (see Bug #1329082 ) - a bug I haven't been able to
replicate, but can do so following these steps. LyX now has to be closed.
You can't use it no matter what I do to CopyTo Textures.

Removed added preferences line ...

I started with Copy To Texture off. Slow. Turning it on now invokes Bug
#1329082
! Its like keys are getting stuck in the event buffer. Old keys
come out that were missed when typing new ones. Very strange.

Restart with Copy ToTexture on. Fast. Turning it off. Still Fast. Back
on. Still fast - nope - gave it a minute ... slow again. Turning off copy
to texture fixed it.

Apparently, the preferences change has some effect on this, Copy to
Textures has a dramatic effect - both at the time LyX is started and the
current state, and how long your using it. Its at least 4 different
factors.

I'll keep playing with this later. Any ideas on specific tests you'd like
me to try? Its hurting my brain!

On Tue, Jul 22, 2014 at 2:43 AM, Jean-Marc Lasgouttes <
<email address hidden>> wrote:

> With my LyX developer hat on:
>
> It is known indeed that LyX has problems with the way display is handled.
> Unfortunately,
> nobody is has the right amount of knowledge and free time to fix that
> currently.
>
> I would be interested to know what happens if you add to your preferences
> file (usually in the ~/.lyx directory) the
> line:
> \use_qimage false
>
> This will make LyX use a Pixmap (that lives in the display server)
> instead of an image which lives in main memory.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/353449
>
> Title:
> lyx 1.6.x impossibly slow
>
> Status in “lyx” package in Ubuntu:
> Confirmed
>
> Bug description:
> Binary package hint: lyx
>
> I am using lyx 1.6.1 on Ubuntu 8.10. This program used to be my do-
> everything software, but it has become unusably slow. That is,
> keystrokes are even delayed in displaying when I type. The rest of
> the system is fine, and LyX didn't used to have such a problem. I'm
> not sure where to start in debugging this.
>
> apt-cache policy lyx
> lyx:
> Installed: 1.6.1-1~intrepid1
> Candidate: 1.6.1-1
> Version table:
> 1.6.1-1 0
> 500 http://ca.archive.ubuntu.com jaunty/universe Packages
> *** 1.6.1-1~intrepid1 0
> 100 /var/lib/dpkg/status
>
>
> lsb_release -rd
> Description: Ubuntu 8.10
> Release: 8.10
>
> To manage notifications about this bug go to:
> https://bugs.l...

Read more...

Revision history for this message
Jean-Marc Lasgouttes (jmarc) wrote :

I would not try to change compiz settings while LyX is running. You are hurting yourself just for the pleasure of it :)

Could you give a synthetic report about the 2*2 possible settings of LyX*Compiz ?

Revision history for this message
Jean-Marc Lasgouttes (jmarc) wrote :

The quote I was looking for is:

SMITH: Doctor, it hurts when I do this.
DALE: Don't do that.

Revision history for this message
Evan Langlois (uudruid74) wrote :

Sometimes doing things that no sane person would do gives insights.
Othertimes, it just hurts more.

For some odd reason, it seems to be behaving exactly the opposite of how it
was behaving initially as far as "Copy To Texture", but maybe I had it in a
different state when LyX started up. The following tests were done by
setting the given settings, loading LyX, opening a 100+ page document,
scrolling up and down a bit, and then starting a new paragraph and banging
away like a mad monkey and seeing how well it keeps up. I also looked at
scroll speed and ended by typing a sentence to see if it was in a "losing
keystrokes" state. If it couldn't keep up, it was marked "Slow", if it
kept up, it is "Fast". Sometimes, the performance would change and get
slower or faster, and I tested everything again when this happened.
Sometimes it would get to the point where it would lose keystrokes - it
actually looked like some sort of buffer overflow. Once it loses a
keystroke, you have to hit a key to get the one it lost. I marked Bug
#1329082
<https://bugs.launchpad.net/bugs/1329082> as a duplicate as this
is definately what I was seeing before.

I'm 80% sure these problems don't appear on the binary ATI driver, but I'm
not willing to re-install it to find out just yet. Getting rid of it was
like pulling teeth.

Most Consistent Results:
----------------------------------
Copy To Texture ON ON OFF OFF
use_qimage false true false true
Speed fast slow slow slow

The only winner seems to be to have qimage to false and copy to texture
on. Anyone else want to verify this?

On Tue, Jul 22, 2014 at 9:37 AM, Jean-Marc Lasgouttes <
<email address hidden>> wrote:

> I would not try to change compiz settings while LyX is running. You are
> hurting yourself just for the pleasure of it :)
>
> Could you give a synthetic report about the 2*2 possible settings of
> LyX*Compiz ?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/353449
>
> Title:
> lyx 1.6.x impossibly slow
>
> Status in “lyx” package in Ubuntu:
> Confirmed
>
> Bug description:
> Binary package hint: lyx
>
> I am using lyx 1.6.1 on Ubuntu 8.10. This program used to be my do-
> everything software, but it has become unusably slow. That is,
> keystrokes are even delayed in displaying when I type. The rest of
> the system is fine, and LyX didn't used to have such a problem. I'm
> not sure where to start in debugging this.
>
> apt-cache policy lyx
> lyx:
> Installed: 1.6.1-1~intrepid1
> Candidate: 1.6.1-1
> Version table:
> 1.6.1-1 0
> 500 http://ca.archive.ubuntu.com jaunty/universe Packages
> *** 1.6.1-1~intrepid1 0
> 100 /var/lib/dpkg/status
>
>
> lsb_release -rd
> Description: Ubuntu 8.10
> Release: 8.10
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/lyx/+bug/353449/+subscriptions
>

Revision history for this message
Jean-Marc Lasgouttes (jmarc) wrote :

Thanks a lot for veryfying this. Would you say that using these 'fast' setting is a good solution or are there drawbacks for other applications?

Revision history for this message
Jean-Marc Lasgouttes (jmarc) wrote :

Another thing to try: lauch LyX with option -graphicssystem raster

This uses a different rendering path in Qt, supposedly faster.

If you come up with something, you can add it to our wiki, presumable here:
http://wiki.lyx.org/LyX/LyXOnUbuntu

Revision history for this message
Evan Langlois (uudruid74) wrote :

Honestly, I have no idea what Copy To Texture was set to before I killed
the proprietary driver. I could never see a difference turning it on
before. But, trying to get rid of the driver lost OpenGL until I fixed it,
and that made Compiz turn off half a dozen plugins. So - who knows how
things worked before.

I have no problem leaving it on. I think its slower to have on if you are
low on RAM maybe - and I have 8GB - 7.2GB after the on-board video (its a
laptop) steals some, or maybe its a software workaround for texture-size
limitations? I dunno.

Of course, the next guy may get totally different performance with these
settings :) It may not be as fast as the proprietary drivers, but its
close enough.

On Tue, Jul 22, 2014 at 2:54 PM, Jean-Marc Lasgouttes <
<email address hidden>> wrote:

> Thanks a lot for veryfying this. Would you say that using these 'fast'
> setting is a good solution or are there drawbacks for other
> applications?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/353449
>
> Title:
> lyx 1.6.x impossibly slow
>
> Status in “lyx” package in Ubuntu:
> Confirmed
>
> Bug description:
> Binary package hint: lyx
>
> I am using lyx 1.6.1 on Ubuntu 8.10. This program used to be my do-
> everything software, but it has become unusably slow. That is,
> keystrokes are even delayed in displaying when I type. The rest of
> the system is fine, and LyX didn't used to have such a problem. I'm
> not sure where to start in debugging this.
>
> apt-cache policy lyx
> lyx:
> Installed: 1.6.1-1~intrepid1
> Candidate: 1.6.1-1
> Version table:
> 1.6.1-1 0
> 500 http://ca.archive.ubuntu.com jaunty/universe Packages
> *** 1.6.1-1~intrepid1 0
> 100 /var/lib/dpkg/status
>
>
> lsb_release -rd
> Description: Ubuntu 8.10
> Release: 8.10
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/lyx/+bug/353449/+subscriptions
>

Revision history for this message
Evan Langlois (uudruid74) wrote :

Well, I tried it. Seemed to work, played with all previous options and
none of them could reproduce the bug. So .. to make sure that it was the
-graphicssystem raster option that fixed it, I tried to reproduce the bug
without this option .. and couldn't :/ I have changed nothing. Haven't
even been at the computer. No idea whats going on.

If I can reproduce again, I'll test again.

On Tue, Jul 22, 2014 at 3:06 PM, Jean-Marc Lasgouttes <
<email address hidden>> wrote:

> Another thing to try: lauch LyX with option -graphicssystem raster
>
> This uses a different rendering path in Qt, supposedly faster.
>
> If you come up with something, you can add it to our wiki, presumable here:
> http://wiki.lyx.org/LyX/LyXOnUbuntu
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/353449
>
> Title:
> lyx 1.6.x impossibly slow
>
> Status in “lyx” package in Ubuntu:
> Confirmed
>
> Bug description:
> Binary package hint: lyx
>
> I am using lyx 1.6.1 on Ubuntu 8.10. This program used to be my do-
> everything software, but it has become unusably slow. That is,
> keystrokes are even delayed in displaying when I type. The rest of
> the system is fine, and LyX didn't used to have such a problem. I'm
> not sure where to start in debugging this.
>
> apt-cache policy lyx
> lyx:
> Installed: 1.6.1-1~intrepid1
> Candidate: 1.6.1-1
> Version table:
> 1.6.1-1 0
> 500 http://ca.archive.ubuntu.com jaunty/universe Packages
> *** 1.6.1-1~intrepid1 0
> 100 /var/lib/dpkg/status
>
>
> lsb_release -rd
> Description: Ubuntu 8.10
> Release: 8.10
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/lyx/+bug/353449/+subscriptions
>

Revision history for this message
Jean-Marc Lasgouttes (jmarc) wrote :

A t least, yu end up in the desirable scenario. It could have been worse :)

Revision history for this message
Evan Langlois (uudruid74) wrote :

I managed to get the bug back - not sure why its intermittent. I've been
playing with it for hours and if I bang away like a mad monkey for 5 or 6
lines, then it enters an "extra-slow" mode where it misses keypresses. I'm
guessing some sort of race condition. Its easier to trigger when the
system is busiest and acting slow. But Copy To Texture is still the best
bet. It seemed like setting graphicssystem to raster made things worse.

On Tue, Jul 22, 2014 at 3:06 PM, Jean-Marc Lasgouttes <
<email address hidden>> wrote:

> Another thing to try: lauch LyX with option -graphicssystem raster
>
> This uses a different rendering path in Qt, supposedly faster.
>
> If you come up with something, you can add it to our wiki, presumable here:
> http://wiki.lyx.org/LyX/LyXOnUbuntu
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/353449
>
> Title:
> lyx 1.6.x impossibly slow
>
> Status in “lyx” package in Ubuntu:
> Confirmed
>
> Bug description:
> Binary package hint: lyx
>
> I am using lyx 1.6.1 on Ubuntu 8.10. This program used to be my do-
> everything software, but it has become unusably slow. That is,
> keystrokes are even delayed in displaying when I type. The rest of
> the system is fine, and LyX didn't used to have such a problem. I'm
> not sure where to start in debugging this.
>
> apt-cache policy lyx
> lyx:
> Installed: 1.6.1-1~intrepid1
> Candidate: 1.6.1-1
> Version table:
> 1.6.1-1 0
> 500 http://ca.archive.ubuntu.com jaunty/universe Packages
> *** 1.6.1-1~intrepid1 0
> 100 /var/lib/dpkg/status
>
>
> lsb_release -rd
> Description: Ubuntu 8.10
> Release: 8.10
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/lyx/+bug/353449/+subscriptions
>

Revision history for this message
Evan Langlois (uudruid74) wrote :

Any progress? Copy To Texture isn't helping anymore and if I don't type slowly, it starts dropping characters and giving me non-sense. The whole input buffer gets trashed.

Revision history for this message
Scott Kostyshak (scott-kostyshak) wrote :

Thanks for the feedback. There has been no progress. If you want though, you can try the development version of LyX. To do that, try the daily PPA: http://wiki.lyx.org/LyX/LyXOnUbuntu#toc3

I don't think it will fix this issue, but if you want to take 1% chance that it will fix the issue, and a 80% it will break other things, give it a shot :)

Revision history for this message
Evan Langlois (uudruid74) wrote :

I'm desperate - I already did it. Worse .. I didn't know the file
format changed, so now I can't go back for the file I'm working on.
The old version of LyX no longer reads it! *sigh*

On Sun, Aug 3, 2014 at 9:41 PM, Scott Kostyshak <email address hidden> wrote:
> Thanks for the feedback. There has been no progress. If you want though,
> you can try the development version of LyX. To do that, try the daily
> PPA: http://wiki.lyx.org/LyX/LyXOnUbuntu#toc3
>
> I don't think it will fix this issue, but if you want to take 1% chance
> that it will fix the issue, and a 80% it will break other things, give
> it a shot :)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/353449
>
> Title:
> lyx 1.6.x impossibly slow
>
> Status in “lyx” package in Ubuntu:
> Confirmed
>
> Bug description:
> Binary package hint: lyx
>
> I am using lyx 1.6.1 on Ubuntu 8.10. This program used to be my do-
> everything software, but it has become unusably slow. That is,
> keystrokes are even delayed in displaying when I type. The rest of
> the system is fine, and LyX didn't used to have such a problem. I'm
> not sure where to start in debugging this.
>
> apt-cache policy lyx
> lyx:
> Installed: 1.6.1-1~intrepid1
> Candidate: 1.6.1-1
> Version table:
> 1.6.1-1 0
> 500 http://ca.archive.ubuntu.com jaunty/universe Packages
> *** 1.6.1-1~intrepid1 0
> 100 /var/lib/dpkg/status
>
>
> lsb_release -rd
> Description: Ubuntu 8.10
> Release: 8.10
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/lyx/+bug/353449/+subscriptions

Revision history for this message
Scott Kostyshak (scott-kostyshak) wrote :

File > Export > 2.1.x will convert it to 2.1.x. You can even convert to older formats in the File > Export > More Formats & Options men.

Revision history for this message
Christopher Barrington-Leigh (cpbl) wrote :

Version 2.2.1 on Ubuntu 16.04: scrolling is still very slow. No other applications on my OS behave like this.

Revision history for this message
Christopher Barrington-Leigh (cpbl) wrote :

Sorry -- I meant to add that using "-graphicssystem raster" only makes it worse.

Revision history for this message
full name (grg2rsr) wrote :

I am suffering from this bug too. While scrolling, Xorgs cpu usage increases (moderatly), while the process lyx uses 100% CPU. Scrolling too far causes the window to grey out, typing text becomes impossibly complicated due to the lag. None of the proposed fixes above changes anything for me ...

@lyx-devs, is there anything I can do to provide tests that can help? This is breaking lyx usability for me, and it's not a piece of software I'd like to sacrifice with a shrug.

Lyx 2.2.2 on Ubuntu 16.10
Xeon 3GHz Quadcore, 16 GB ram
NVIDIA Quadro FX 5600

Revision history for this message
full name (grg2rsr) wrote :

I just saw [here](https://bugs.launchpad.net/ubuntu/+source/lyx/+bug/129813) that this might be related to more general NVIDIA related X issues, that are [supposedly solved in the latest X 1.19](https://devtalk.nvidia.com/default/topic/976844/xorg-1-19-support/). I am on a fresh test install of Ubuntu 17.04 using the 340.102 driver now ([which supports X 1.19](https://www.phoronix.com/scan.php?page=news_item&px=NVIDIA-Legacy-6-Fermi-1.19))and confirm that lyx performance is good.

Revision history for this message
Radomír Černoch (radomir-cernoch) wrote :

I'm running Ubuntu 17.04 with the 375.66 driver and GeForce 1080. LyX's performance on my machine is very bad, exactly as described above. Scrolling and typing make the Xorg process use 100% CPU.

I'd be happy to help by testing.

Revision history for this message
Scott Kostyshak (scott-kostyshak) wrote :

You can test LyX's development version (do not use for any serious work and expect the worst) by using this PPA:

https://launchpad.net/~lyx-devel/+archive/ubuntu/daily

Install the lyx2.3pre package.

Whether it fixes the issues or does not fix the issues, the developers would be very interested in knowing. Please write an email to <email address hidden> and reference this bug.

Sorry for the annoying slowness, and thanks a lot for your offer to help test!

Revision history for this message
Jean-Marc Lasgouttes (jmarc) wrote :

Even better, you could try to test latest master of LyX, where a new screen painting strategy has been implemented. This may eventually be backported to the 2.3 series at a later time.

Revision history for this message
Jean-Marc Lasgouttes (jmarc) wrote :

For what is worth, the new update mechanism has been ported to LyX 2.3.1. Currently, this is only available on Disco, which has LyX 2.3.2. It is of course available through the ppa for older versions. I would be very interested to know whether this new scheme (basically "do things as it should have been done from the start") helps.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.