882918 - Defect - Pages/Chrome don't respond to events

Status: RESOLVED DUPLICATE of bug 931743

(Firefox for Metro Graveyard :: Browser, defect, P2)

Description

[Richard Newman [:rnewman]]

Open a pull request. Click "Files changed" to get a diff view.

Now try to do anything. Scroll with your finger, for example. Observe that the UI totally hangs; no finger scrolling, keyboard scrolling, selection, scrollbar action. If you're lucky, doing something like tapping with a stylus will unlock the UI for a few hundred milliseconds, giving it just enough time to jump to another part of the page.

This might just be a particularly bad version of the wider "if there's any JS in the page, Metro is almost unusably slow" issue; not sure.

Comment 1

[Richard Newman [:rnewman]]

Video:

http://www.youtube.com/watch?v=pV1Yc4nO8hs

Comment 2

[Brian R. Bondy [:bbondy]]

I think this is another manifestation of the bug where touch input sometimes stops working.

Comment 3

[Brian R. Bondy [:bbondy]]

Was this using a release build or a debug build?

Comment 4

[Richard Newman [:rnewman]]

Official Nightly.

Comment 5

[Richard Newman [:rnewman]]

(In reply to Brian R. Bondy [:bbondy] from comment #2)
> I think this is another manifestation of the bug where touch input sometimes
> stops working.

It seems that way; just hit the same behavior on <http://rideapart.com/2013/07/the-5-best-motorcycle-roads-in-america>, so it's not limited to GH.

Comment 6

[Brian R. Bondy [:bbondy]]

Is this still happening on today's (or later) nightly?

Comment 7

[Richard Newman [:rnewman]]

(In reply to Brian R. Bondy [:bbondy] from comment #6)
> Is this still happening on today's (or later) nightly?

Things seem to be *a lot* more responsive today. Can't conclusively verify (I'll keep my eyes open), but it seems to be resolved...

What was the cause, out of interest?

Comment 8

[Brian R. Bondy [:bbondy]]

Possibly bug 890362

Comment 9

[Richard Newman [:rnewman]]

I just had essentially this exact experience with 07/23 Nightly on the Gmail 2-factor auth screen. Tapping, clicking, typing did nothing... until I hit the Windows button. As the app faded away (and the event loop cleared?), I saw the numbers I had typed appear in the box.

Reopening this rather than comment on a dead bug, but feel free to morph/dupe.

Comment 10

[Tim Abraldes [:TimAbraldes] [:tabraldes]]

I wonder if this is related to bug 840855 or perhaps bug 896896.

It's a little frightening how frequently we seem to be dropping input messages. Perhaps we should do some kind of audit of all of our Windows message-handling code in metro?