Profiler doesn't work with a Flame with Firefox OS 2.0

RESOLVED FIXED

Status

()

Firefox
Developer Tools: Performance Tools (Profiler/Timeline)
RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: marco, Unassigned)

Tracking

Trunk
x86_64
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

3 years ago
I'm trying to use the profiler with a Flame (Firefox OS 2.0). I can start the profile, but I can't stop it. This is the error I'm seeing in the browser console:

> A promise chain failed to handle a rejection. Did you forget to '.catch', or did you forget to 'return'?
> See https://developer.mozilla.org/Mozilla/JavaScript_code_modules/Promise.jsm/Promise
> 
> Date: Sat Jan 17 2015 00:13:39 GMT+0100 (CET)
> Full Message: Protocol error (unrecognizedPacketType): Actor conn7.child3/framerate14 does not recognize the packet type getPendingTicks
> Full Stack: JS frame :: resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js :: PendingErrors.register :: line 165
> JS frame :: resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js :: this.PromiseWalker.completePromise :: line 678
> JS frame :: resource://gre/modules/Task.jsm :: TaskImpl_handleException :: line 448
> JS frame :: resource://gre/modules/Task.jsm :: TaskImpl_run :: line 326
> JS frame :: resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js :: Handler.prototype.process :: line 873
> JS frame :: resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js :: this.PromiseWalker.walkerLoop :: line 749
> JS frame :: resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js :: this.PromiseWalker.scheduleWalkerLoop/< :: line 691
> native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0
The new profiler (performance) tool, which will be made available in Fx39, should fix this from bug 1130200
This should be resolved in latest nightly profiler, with B2G 2.0-2.2. Please reopen if this is not the case. Thanks!
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.