Open Bug 732872 Opened 8 years ago Updated 2 years ago

Firefox runs extremely slowly when Windows Speech Recognition is running [meta]

Categories

(Firefox :: Disability Access, defect, major)

7 Branch
x86_64
Windows 7
defect
Not set
major

Tracking

()

People

(Reporter: mtrigoboff, Unassigned)

References

(Blocks 2 open bugs)

Details

(Keywords: meta, perf, Whiteboard: [Q2 goal])

Attachments

(1 file)

Attached image sysinfo.jpg
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1
Build ID: 20110928134238

Steps to reproduce:

Due to wrist tendon problems, I have started using Windows Speech Recognition and Windows Speech Recognition Macros. In this situation, if I open more than two tabs in Firefox, the browser slows to a crawl. It's painfully slow. This does not happen in, for instance, Chrome. I've attached a screen shot displaying my system information.
Component: Untriaged → Disability Access
QA Contact: untriaged → disability.access
Another report on the web http://www.speechcomputing.com/node/2720. It sounds MSAA support it guilty.
(In reply to Michael Trigoboff from comment #0)
> Due to wrist tendon problems, I have started using Windows Speech
> Recognition and Windows Speech Recognition Macros. In this situation, if I
> open more than two tabs in Firefox, the browser slows to a crawl. It's
> painfully slow. This does not happen in, for instance, Chrome. I've attached
> a screen shot displaying my system information.

Could you please provide simple steps to reproduce the problem? English is not my native language and I had hard times to fight with WSR.
(In reply to alexander :surkov from comment #2)
> (In reply to Michael Trigoboff from comment #0)
> > Due to wrist tendon problems, I have started using Windows Speech
> > Recognition and Windows Speech Recognition Macros. In this situation, if I
> > open more than two tabs in Firefox, the browser slows to a crawl. It's
> > painfully slow. This does not happen in, for instance, Chrome. I've attached
> > a screen shot displaying my system information.
> 
> Could you please provide simple steps to reproduce the problem? English is
> not my native language and I had hard times to fight with WSR.

1) Install and run Windows Speech Recognition.
2) Install and run Windows Speech Recognition Macros.
3) Open Firefox and then open 5 tabs.

On my machine, this slows Firefox to a crawl.
(In reply to Michael Trigoboff from comment #3)

> On my machine, this slows Firefox to a crawl.

is it slow on WSR commands or slow on keyboard/mouse?
Firefox becomes very slow in its response to the keyboard and mouse.
there's no single bottleneck here, UIAutomation just inspects the tree. From what I've seen sometimes we spend up to 30% for accessible states calculation, 25% is spend by UIAutomationCore.dll (no in Firefox calls).

we need bug assignee.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Whiteboard: [Q2 candidate]
We need a test so that we can measure fixage.
Whiteboard: [Q2 candidate] → [Q2 goal]
I've trained speech rec on my Windows machine. Firefox is slower but usable, although my machine is pretty beefy. I hope to run some profiling next but it sounds like Alexander already has.

Alexander what can we do here?

Note a possible separate bug: advanced text edit WSR commands don't work in our edit boxes.
No noticeable slowdown in IE.
I'm the one who originally reported this bug. My machine's pretty beefy too. Intel Core i7 950, Intel SSD, 6 gig RAM. My problem may be that I like to open 20 - 30 tabs sometimes. This worked fine for me until I started using WSR and WSR Macros.
(In reply to Michael Trigoboff from comment #10)
> I'm the one who originally reported this bug. My machine's pretty beefy too.
> Intel Core i7 950, Intel SSD, 6 gig RAM. My problem may be that I like to
> open 20 - 30 tabs sometimes. This worked fine for me until I started using
> WSR and WSR Macros.

Yes thanks. My comment 9 was ambiguous but I was noticing that FF does slow down with WSR much more significantly than IE. There is definitely churn and I suspect lack of UIA implementation is to blame (as per comment 6), since we need to use the MS proxy.
(In reply to David Bolter [:davidb] from comment #8)
> I hope to run some profiling next but
> it sounds like Alexander already has.

yes, see comment #6

> Alexander what can we do here?

We have two options here:
1) implement basics of UIA to avoid State() calls
2) rearchitect states getting

in general we need to do both.
Depends on: 754830
Depends on: 754857
Depends on: 756381
Depends on: 754879
Depends on: 756383
The build on top of all blocking bugs (the latest one is bug 756383), I don't see big lags when scrolling (there are problems on loading still). So basically we've got good perf improvement.
No longer depends on: 756383
Depends on: 756383
Depends on: 756969
Depends on: 756973
Depends on: 756975
Depends on: 756983
Depends on: 757670
Keywords: meta, perf
Summary: Firefox runs extremely slowly when Windows Speech Recognition is running → Firefox runs extremely slowly when Windows Speech Recognition is running [meta]
(In reply to alexander :surkov from comment #13)
> The build on top of all blocking bugs (the latest one is bug 756383), I
> don't see big lags when scrolling (there are problems on loading still). So
> basically we've got good perf improvement.

All th eblocking bugs are fixed. So is are the issues associated with this era essentially finished off?
Severity: normal → major
Flags: needinfo?(surkov.alexander)
(In reply to Wayne Mery (:wsmwk, use Needinfo for questions) from comment #14)
> (In reply to alexander :surkov from comment #13)
> > The build on top of all blocking bugs (the latest one is bug 756383), I
> > don't see big lags when scrolling (there are problems on loading still). So
> > basically we've got good perf improvement.
> 
> All th eblocking bugs are fixed. So is are the issues associated with this
> era essentially finished off?

we'd need to get some feedback how it feels now before calling it done.  Michael, can you give it a try please?
Flags: needinfo?(surkov.alexander)
Flags: needinfo?(mtrigoboff)
Flags: needinfo?
(In reply to alexander :surkov from comment #15)
> (In reply to Wayne Mery (:wsmwk, use Needinfo for questions) from comment
> #14)
> > (In reply to alexander :surkov from comment #13)
> > > The build on top of all blocking bugs (the latest one is bug 756383), I
> > > don't see big lags when scrolling (there are problems on loading still). So
> > > basically we've got good perf improvement.
> > 
> > All th eblocking bugs are fixed. So is are the issues associated with this
> > era essentially finished off?
> 
> we'd need to get some feedback how it feels now before calling it done. 
> Michael, can you give it a try please?

I've been in touch with Michael and he is no longer using Firefox. NI:surkov to decide disposition of bug.
Flags: needinfo?(surkov.alexander)
Flags: needinfo?(mtrigoboff)
Flags: needinfo?
We still have perf problems overall in the a11y engine, I would suggest to keep this bug open until the major a11y bottlenecks are resolved. Then we can revisit this bug and make decision on it.
Flags: needinfo?(surkov.alexander)
(In reply to alexander :surkov from comment #17)
> We still have perf problems overall in the a11y engine, I would suggest to
> keep this bug open until the major a11y bottlenecks are resolved. Then we
> can revisit this bug and make decision on it.

Hello, 

Like Michael, I've recently started using microsoft speech recognition due to problems with my wrist and fingers. Firefox is pretty unusable with speech recognition. I do not have a beefy computer, but previously I would have >10 tabs open with no significant issue. With speech recognition turned on, Firefox becomes barely usable. Even scrolling through reddit is a problem, with it increasingly lagging, causing all of firefox to become unresponsive (even with a mouse) until I close speech recognition.

I'm unfortunately going to switch to chrome because of this. However, if you've had 2 people report this bug, I'm sure a whole lot more are experiencing this issue and being forced away from Firefox :(

Thanks, 
Jason
Just to add to my above comment... when I look at the resource monitor everything seems fine (CPU & memory are nowhere near 100% utilization)
I am entering this text using Windows Speech Recognition, and Firefox currently probably has more than 100 open tabs.  The browser seems to be operating pretty well.

Using 55.0a1 (2017-05-25) (32-bit)
You need to log in before you can comment on or make changes to this bug.