Closed Bug 1001454 Opened 10 years ago Closed 10 years ago

[b2gperf] Unable to flick through homescreen pages

Categories

(Remote Protocol :: Marionette, defect, P1)

x86
macOS
defect

Tracking

(b2g-v1.4 fixed)

RESOLVED FIXED
Tracking Status
b2g-v1.4 --- fixed

People

(Reporter: davehunt, Assigned: mdas)

References

Details

(Keywords: pi-marionette-server)

Attachments

(1 file)

b2gperf has been unable to flick through the homescreen pages to gather FPS results since April 11th. I was able to narrow the regression range down to:

Gecko good: d41e6e32df81
Gecko bad: 783c5013dbec
Gecko pushlog: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=d41e6e32df81&tochange=783c5013dbec

There were no changes in Gaia between these two tinderbox builds.

I strongly suspect bug 958036 has caused this to regress.
:mdas this still appears to be an issue. I can replicate using the following:

$ b2gperf --test-type=scrollfps --reset Homescreen

Are you able to replicate this?
Flags: needinfo?(mdas)
Assignee: nobody → mdas
Flags: needinfo?(mdas)
Priority: -- → P1
It's definitely related to the apz code. In the logcat, we have:

E/GeckoConsole(  618): [JavaScript Error: "iframe is undefined" {file: "chrome://marionette/content/marionette-listener.js" line: 120}]

when attempting to emit the touch events, which is from the new code. I'll investigate this now.
When passing frameId (which is the index into window.frames) of 0, this line would assign it to null and would cause problems later on when we tried to use that frameId to inject touch events into it via the root process.
Attachment #8418863 - Flags: review?(dburns)
Btw, I'm not sure why we did that conditional assignment, it doesn't seem to really do anything. I'm running through try to verify

try for emulator Mn, webapi:
https://tbpl.mozilla.org/?tree=Try&rev=8e0c8a7929be

try for Gu:
https://tbpl.mozilla.org/?tree=Try&rev=826b615c22e2
Component: General → Marionette
tries are green
Attachment #8418863 - Flags: review?(dburns) → review+
landed as:

https://hg.mozilla.org/mozilla-central/rev/d74281e6d571

I landed it with the wrong bug number in the commit :(
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Product: Testing → Remote Protocol
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: