Open Bug 1714053 Opened 3 years ago Updated 2 years ago

Tab get's stuck when buying stuff on


(GeckoView :: General, defect, P3)



(Not tracked)


(Reporter: petru, Unassigned)



From github:

Steps to reproduce

  1. Open
  2. Login
  3. Add something to cart
  4. Try to buy it

Expected behavior

I can finish buying it

Actual behavior

Firefox content process uses 100% cpu and I cannot interact with page at all
Here is a performance profile of it:

Device information

  • Device vendor / model and Android version: Samsung Galaxy J7 2017
  • Firefox for Android version: Firefox nightly 90.0a1 (Build #2015813833), happens on release as well.

I reported a very similar (or same) issue here, but it previously stopped reproducing, but now it's back:

Change performed by the Move to Bugzilla add-on.

Lots of time spent on touchmove events so maybe DOM or the website is poorly coded?

Component: General → DOM: Events
Product: GeckoView → Core
Summary: [Bug] Tab get's stuck when buying stuff on → Tab get's stuck when buying stuff on
Component: DOM: Events → DOM: UI Events & Focus Handling

Edgar: can you please help triaging this?

Flags: needinfo?(echen)

touchmove event handler seem to not take too much time, 20~30 ms per event.
But I noticed that there is a lot of deviceorientation and devicemotion event get fired.
Not sure if it is normal that devices keeps sending deviceorientation and devicemotion event so frequently.
Since they are from Android Hal, switch bug to Widget: Android to see if someone could take a look.
(Please feel free to swtich to other component if it is not the right one)

Component: DOM: UI Events & Focus Handling → Widget: Android
Flags: needinfo?(echen)

Moving all open Core::Widget: Android bugs to GeckoView::General (then the triage owner of GeckoView will decide which ones are valuable and which ones should be closed).

Component: Widget: Android → General
Product: Core → GeckoView
Blocks: 1697647
Priority: -- → P3
No longer blocks: 1697647
Depends on: 1697647
Severity: -- → S3
You need to log in before you can comment on or make changes to this bug.