Closed Bug 1095452 Opened 11 years ago Closed 11 years ago

Errors are thrown in the console after closing the 2nd window in which Timeline was running

Categories

(DevTools :: Performance Tools (Profiler/Timeline), defect)

35 Branch
defect
Not set
normal

Tracking

(firefox35 affected, firefox36 affected)

RESOLVED WORKSFORME
Tracking Status
firefox35 --- affected
firefox36 --- affected

People

(Reporter: avaida, Unassigned)

References

Details

Reproducible on: * Aurora 35.0a2 (2014-11-04), * Nightly 36.0a1 (2014-11-04), using Windows 7 64-bit, Ubuntu 14.04 LTS 64-bit and Mac OS X 10.8.5. STR: 1. Launch Firefox using a clean profile. 2. Enable Timeline from the Developer Tools. 3. Click menu → New Window. 4. Open the Browser Console from the Developer Tools. 5. Access a content-heavy website in the 2nd window - (e.g.) http://themify.me/demo/themes/parallax/ 6. Start recording operations in Timeline for a few seconds, then stop recording. 7. Close the 2nd window and check the console. Expected result: there are no errors thrown for these actions. Actual result: three JS errors are thrown in the console after closing the 2nd window in which Timeline was running - http://pastebin.mozilla.org/7125786. Additional information: - These errors are being thrown across platforms (Windows, Linux, Mac).
Flags: qe-verify+
Copying over the errors for safekeeping: "Protocol error (noSuchActor): No such actor for ID: conn3.timelineActor77" in protocol.js:18 "Protocol error (noSuchActor): No such actor for ID: conn3.timelineActor77" in Promise-backend.js:868 IndexedDB UnknownErr: IDBDatabase.cpp:776
Moving into the Profiler component. Filter on GUTHRIE'S WAVY CAKES.
Component: Developer Tools: Timeline → Developer Tools: Profiler
Please test again with the new perf tool, and reopen if this is still an issue. Thanks!
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.