62549 - text entry into forms is CPU intensive.

Status: VERIFIED DUPLICATE of bug 58148

(Core :: Layout: Form Controls, defect, P1)

Description

[Ben Woodard]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.17 i686; en-US; m18) Gecko/20001209
BuildID:    cvs-12/10/00

For some reason, just entering text into a form ends up being CPU intensive.
This is quite noticable for me because my laptop has a fan in it that is off
most of the time but which kicks in when CPU utilization is high.

Reproducible: Always
Steps to Reproduce:
Type a bunch of text into the a form while running top.

Actual Results:  You will see that mozilla is using a huge amount of CPU while
just accepting keystrokes into a form.


Expected Results:  Keyboard input takes minimal CPU.

Comment 1

[rods (gone)]

reassinging

Comment 2

[Fabian Guisset]

*** Bug 62547 has been marked as a duplicate of this bug. ***

Comment 3

[rubydoo123]

assigning to anthonyd and cc sfraser (to track for the embed work)

Comment 4

[anthonyd]

well, this does happen.  i did a little testing (all on windows), here are the 
results:
typing in notepad: cpu hits 2%
typing in textfield on IE: cpu hits 11%
typing in textfield NOT in a table: cpu hits 50%
typing in textfield in a table: cpu hits 89%

really, really bad.  but we all know where the real problem here is, but ill 
wait to say it untill i have profile data to prove it yet again.

anthonyd

Comment 5

[Ben Woodard]

> we all know where the real problem here is

'cept me. I don't know what the real problem is. What is it? I'm curious. Is it
the code that takes the events for the windows and figures out what piece of
code actually needs to handle the event?

Comment 6

[Vladimir Ermakov]

QA Contact Update

Comment 7

[anthonyd]

keeping this open for 0.9 because before buster left he checked in some layout 
code that will hopefully fix this.  His fix especially addresses the problem 
when in tables.

anthonyd (needing to re-test)

Comment 8

[anthonyd]

setting platform and os to all, even though thhis was first reported on linux, 
it exists everywhere.

anthonyd

Comment 9

[rubydoo123]

moving this out to mozilla0.9.1 where we can spend a bit more time on this

Comment 10

[Kathleen :Brade]

Move this to mozilla0.9.2; anyone should feel free to help Tony out with this bug 
(unless he moves it back to 0.9.1).

Ben Woodard--do you still see the cpu hit?

Comment 11

[Daniel Mario Vega (Restore MNG Support --> #18574)]

I think this is a duplicate of bug 58148

Comment 12

[Simon Fraser [no longer active]]

Yup.


*** This bug has been marked as a duplicate of 58148 ***

Comment 13

[Vladimir Ermakov]

verifying