Juergen Vigna <[EMAIL PROTECTED]> writes:
| On 18-Mar-2002 Lars Gullik Bjønnes wrote:
>
>> I do not get a crash.
>
| I don't get a crash too!
>
>> I get a hang until I release the mouse button, then everything works
>> again...
>>
>> So... for me this is down to a minor bug now.
>
| Well if you say a permantent load of 30-40% of a 1GHz CPU is normal then
| this is an opinion, I don't think so.
Hmm, yes I see this. If I leave the whole document selected (or a
large part of it), then the cpu is at ~70% steady...
And you say that all this is Selection events? I am not sure that this
is the case since X is at ~0%, if X were sending selection events at
us it too should be high on cpu.
So the question is: What is LyX (or XForms) doing when a large part of
the document is selected?
If I run LyX through gdb, then the cpu utilization is not there at all
and is down to ~0% even with large parts of the document selected...
One thing I then would like to check is if we receive a lot of
signals... signals that we ignore perhaps?
Hmm this was not true either... if I select with the mouse then I get
the ~90% cpu. When running lyx with -sync and selectiong with the
mouse then I see:
MainLoop Event(30,w=0x4c0006f s=414088) SelectionRequest
MainLoop Event(30,w=0x4c0006f s=414108) SelectionRequest
MainLoop Event(30,w=0x4c0006f s=414128) SelectionRequest
MainLoop Event(30,w=0x4c0006f s=414148) SelectionRequest
MainLoop Event(30,w=0x4c0006f s=414168) SelectionRequest
MainLoop Event(30,w=0x4c0006f s=414188) SelectionRequest
MainLoop Event(30,w=0x4c0006f s=414208) SelectionRequest
MainLoop Event(30,w=0x4c0006f s=414228) SelectionRequest
MainLoop Event(30,w=0x4c0006f s=414248) SelectionRequest
MainLoop Event(30,w=0x4c0006f s=414268) SelectionRequest
MainLoop Event(30,w=0x4c0006f s=414288) SelectionRequest
MainLoop Event(30,w=0x4c0006f s=414308) SelectionRequest
MainLoop Event(30,w=0x4c0006f s=414328) SelectionRequest
MainLoop Event(30,w=0x4c0006f s=414348) SelectionRequest
MainLoop Event(30,w=0x4c0006f s=414368) SelectionRequ
However this is not what takes time, what takes time is the
selectionAsString that is run for each of them.
Somehow new events are created again and again...
Hmm are all of you running KDE?
Running with and without the Klipper utlitity makes all the difference
here.
So... now somebody else can dig a bit.
--
Lgb
