Justin Pryzby wrote:
> On Mon, May 08, 2006 at 11:41:39AM +0200, Jan Willem Stumpel
> wrote:
>> It has always been difficult to reproduce this for purposes
>> of bug reporting but now I found a fairly reliable way;
>>
>> -start Firefox.
>> -put the cursor in the address window.
>> -hit the "A" key, but somewhat to the left, so you also
>> engage the CapsLock key.
>>
>> You will probably not have to try this more than 2 or 3 times
>> before your system freezes completely with approx. 100% CPU
>> usage by Firefox.
>
> I cannot reproduce this
Aargh. I was afraid of that. I can reproduce it very reliably
though, both in Mozilla and in Firefox. The trouble is, it also
happens when I do not want to trigger it, but hit some key wrongly
by accident.
> but it sure sounds like #360079.
Not quite the same, I think; #360079 does not mention 100% CPU.
And "my" bug does not happen immediately when starting Firefox /
Mozilla; it is only triggered by some keyboard event.
If I try strace I get the usual incomprehensible huge file, which
in this case seems to consist mostly of things like (forever repeated)
poll([{fd=3, events=POLLIN}, {fd=9, events=POLLIN}, {fd=13,
events=POLLIN|POLLPRI}, {fd=15, events=POLLIN|POLLPRI}, {fd=16,
events=POLLIN|POLLPRI}, {fd=17, events=POLLIN|POLLPRI}, {fd=5,
events=POLLIN, revents=POLLIN}], 7, -1) = 1
gettimeofday({1147097643, 645052}, NULL) = 0
read(5, "\372", 1) = 1
ioctl(3, FIONREAD, [0]) = 0
Maybe you can make sense out of this..
> What kind of cursor do you get when this happens? The "xserver
> becomes unusable part" sounds like #361303.
Just the 'vertical bar' cursor which is usual for text fields;
after the bug is triggered it stops flashing, though. The bug only
occurs when the cursor is in the address field, not in any other
text field as far as I could find out. 'top' says that it is
firefox/mozilla which is using the cycles, not some other process.
Regards, Jan
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
