Closed Bug 892928 Opened 11 years ago Closed 11 years ago

b2gperf is failing to gather FPS measurements on mozilla-central builds

Categories

(Firefox OS Graveyard :: General, defect)

ARM
Gonk (Firefox OS)
defect
Not set
major

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: davehunt, Unassigned)

Details

We've recently switched the devices running 'master' performance tests from a mozilla-b2g18 build to a mozilla-central build. This is to be more indicative of the future release based on trunk.

As a result, the FPS measurements are no longer being gathered. From debugging b2gperf it would appear that the following line never returns and therefore we get a timeout:

let utils = window.QueryInterface(Components.interfaces.nsIInterfaceRequestor).getInterface(Components.interfaces.nsIDOMWindowUtils);

From: https://github.com/mozilla/b2gperf/blob/master/b2gperf/scrollapp.js#L26

The following is from logcat after this call:

D/memalloc( 6149): /dev/pmem: Unmapping buffer base:0x44f00000 size:2498560 offset:2457600
D/memalloc( 6149): /dev/pmem: Unmapping buffer base:0x45210000 size:2539520 offset:2498560
I/Gonk    ( 5693): Setting nice for pid 6198 to 18
I/Gonk    ( 5693): Changed nice for pid 6198 from 0 to 18.
E/Profiler( 6198): BEGIN mozilla_sampler_init
E/Profiler( 6198): BPUnw: [1 total] thread_register_for_profiling(me=0x401084f8, stacktop=0xbed85927)
E/Profiler( 6198): SPS:
E/Profiler( 6198): SPS: Unwind mode       = pseudo
E/Profiler( 6198): SPS: Sampling interval = 0 ms (zero means "platform default")
E/Profiler( 6198): SPS: UnwindStackScan   = 0 (max dubious frames per unwind).
E/Profiler( 6198): SPS: Use env var MOZ_PROFILER_MODE=help for further information.
E/Profiler( 6198): SPS:
E/Profiler( 6198): Registering start signal
E/Profiler( 6198): BPUnw: [2 total] thread_register_for_profiling(me=0x7ff1c8, stacktop=0x430d8ec7)
E/GeckoConsole( 6198): Could not read chrome manifest 'file:///system/b2g/chrome.manifest'.
E/Profiler( 5693): BPUnw: [14 total] thread_register_for_profiling(me=0x121fd8, stacktop=0x4a8ffe4f)
E/Profiler( 6198): BPUnw: [3 total] thread_register_for_profiling(me=0x7ff368, stacktop=0x43dffec7)
I/Gecko   ( 6198): ###################################### forms.js loaded
I/Gecko   ( 6198): ############################### browserElementPanning.js loaded
I/Gecko   ( 6198): ######################## BrowserElementChildPreload.js loaded
E/Profiler( 5693): BPUnw: [13 total] thread_unregister_for_profiling(me=0x118998) 
E/Profiler( 5693): BPUnw: [12 total] thread_unregister_for_profiling(me=0x121f98) 
E/Profiler( 5693): BPUnw: [11 total] thread_unregister_for_profiling(me=0x121f18) 
E/Profiler( 5693): BPUnw: [10 total] thread_unregister_for_profiling(me=0x121fd8)
I/Gecko   ( 5693): 1373627439848	Marionette	INFO	sendToClient: {"from":"0","error":{"message":"timed out","status":28,"stacktrace":null}}, {857570e7-f4f6-47f8-942b-fdba358854ab}, {857570e7-f4f6-47f8-942b-fdba358854ab}
...
It wouldn't shock me to find out that this is related to some wrapper change.
I'll see if I can determine a regression range.
Whiteboard: [qa-automation-blocked]
I can replicate in 32c3ccd8946c but not in 43c0123f158b. I can try to reduce this range if anyone is interested, however I noticed that the line in question doesn't appear to be used at all. I've removed it and am currently running the tests with a new version of b2gperf. If this is successful I will release this new version and close this issue.
b2gperf 0.5 released

Fix was to remove the line:
https://github.com/mozilla/b2gperf/commit/c2b6c66963ede05b347c32b9607168ed6095c17d
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Whiteboard: [qa-automation-blocked]
You need to log in before you can comment on or make changes to this bug.