Closed Bug 1327952 Opened 7 years ago Closed 7 years ago

Scrolling in "Share this page" panel is ridiculously slow

Categories

(Firefox Graveyard :: SocialAPI, defect)

48 Branch
defect
Not set
normal

Tracking

(firefox50 wontfix, firefox51 wontfix, firefox52 wontfix, firefox-esr52 fix-optional, firefox53 wontfix, firefox54 fix-optional, firefox55 fix-optional)

RESOLVED WONTFIX
Tracking Status
firefox50 --- wontfix
firefox51 --- wontfix
firefox52 --- wontfix
firefox-esr52 --- fix-optional
firefox53 --- wontfix
firefox54 --- fix-optional
firefox55 --- fix-optional

People

(Reporter: arni2033, Unassigned)

References

Details

(Keywords: regression, Whiteboard: [gfx-noted])

>>>   My Info:   Win7_64, Nightly 49, 32bit, ID 20160526082509
STR_1:
1. Open "Share this page" panel, click Google+
2. Close the panel. Open the panel
3. Hover mouse over the center of the panel and rotate mouse wheel down once

AR:  Scrolling happens after ~15 seconds and isn't smooth
ER:  Scrolling shouls happen immediately

This is regression from bug 1257723. Regression range:
> https://hg.mozilla.org/integration/fx-team/pushloghtml?fromchange=674a552743785c28c75866969aad513bd8eaf6ae&tochange=5467a8d9d844fff2b8916999ebd1f4e90289e2d1@ Shane Caraveo (:mixedpuppy):
It seems that this is a regresion caused by your change. Please have a look.
No longer blocks: 1277113
I can reproduce on Mac OS X 10.10. 

Shane can you please take a look at this, it seems that bug 1257723 cause this regression? Thanks
Component: Untriaged → Panning and Zooming
Flags: needinfo?(mixedpuppy)
Product: Firefox → Core
Priority: -- → P3
Whiteboard: [gfx-noted]
Clearing priority so that this shows up on the triage dashboard once the needinfo is cleared or expires.
Priority: P3 → --
Component: Panning and Zooming → SocialAPI
Flags: needinfo?(mixedpuppy)
Product: Core → Firefox
Flagging :markh as the reviewer of the regressing patch, since the author isn't responding.
Flags: needinfo?(markh)
Basically repeating myself from bug 1327939

How was the regression range found?  Were you using mozregression?

We don't do anything in content, the patch doesn't touch anything with mouse events, etc.
Flags: needinfo?(markh)
(In reply to Shane Caraveo (:mixedpuppy) from comment #4)
> Basically repeating myself from bug 1327939
> 
> How was the regression range found?  Were you using mozregression?
> 

I was able to confirm the regression range using:

mach mozregression --repo fx-team --launch 674a5527 # good version
mach mozregression --repo fx-team --launch 5467a8d9 # bad version

So yes, the regression range is correct, and it doesn't really matter if it was found using mozregression or not. The patch does seem to touch the code exercised in the STR so it seems likely that the patch caused the regression somehow, even if it's not immediately obvious how.
Flags: needinfo?(mixedpuppy)
Version: Trunk → 48 Branch
Flags: needinfo?(mixedpuppy)
closing due to bug 1389630
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
Product: Firefox → Firefox Graveyard
You need to log in before you can comment on or make changes to this bug.