Closed Bug 1095456 Opened 10 years ago Closed 9 years ago

[e10s] Errors are thrown in the console while using Timeline in a e10s window

Categories

(DevTools :: General, defect)

35 Branch
defect
Not set
normal

Tracking

(e10s+, firefox35 affected, firefox36 affected, firefox37 unaffected)

RESOLVED INCOMPLETE
Tracking Status
e10s + ---
firefox35 --- affected
firefox36 --- affected
firefox37 --- unaffected

People

(Reporter: avaida, Unassigned)

References

Details

(Whiteboard: [e10s-m7])

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 e10s Window and access a content-heavy website - (e.g.) http://themify.me/demo/themes/parallax/
4. Open the Browser Console from the Developer Tools.
5. Start recording operations in Timeline using the e10s-enabled window.
6. Stop recording
7. Check the Browser Console.

Expected result: there are no errors thrown in the console while using Timeline in e10s.

Actual result: JS errors are thrown in the console while using Timeline in an e10s-enabled window - http://pastebin.mozilla.org/7125872.

Additional information:
- These errors are being thrown across platforms (Windows, Linux, Mac).
Flags: qe-verify+
This isn't a timeline-related bug. The error in http://pastebin.mozilla.org/7125872 is instead related to the way the devtools server attaches to windows.
No longer blocks: timeline-v1
Component: Developer Tools: Timeline → Developer Tools
These DevTools bugs should probably block e10s from riding to Aurora.
devtools bugs will block the e10s merge to Aurora, but blassey would like them to be tracked by dte10s meta bug 875871, not the tracking-e10s=m6+ flag.
Whiteboard: [e10s-m6]
I tried this today with a recent fx-team build and couldn't reproduce it.
(Sigh) That pastebin appears to have expired, which makes it impossible to see the error. Can anyone who can still reproduce this attach the log to the bug?
(In reply to Panos Astithas [:past] from comment #5)
> (Sigh) That pastebin appears to have expired, which makes it impossible to
> see the error. Can anyone who can still reproduce this attach the log to the
> bug?

Yeah, it seems that the 'Forever' option in pastebin is not really working anymore. Sorry about that. This is the only error I'm still seeing on the builds from Comment 0, using the same steps:

Handler function threw an exception: TypeError: handler.addEventListener is not a function
Stack: DebuggerProgressListener.prototype.watch@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/actors/webbrowser.js:1932:5
TabActor.prototype.observe/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/actors/webbrowser.js:924:11
makeInfallible/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/DevToolsUtils.js:83:14
Line: 1932, column: 4 DevToolsUtils.js:59
Thank you for the stack trace. This appears to be from an older version of the code, I can't reproduce it in 37. Can you verify that it is fixed there?
(In reply to Panos Astithas [:past] from comment #7)
> Thank you for the stack trace. This appears to be from an older version of
> the code, I can't reproduce it in 37. Can you verify that it is fixed there?

I'm not seeing this error message on Nightly 37.0a1 (2014-12-22).
Whiteboard: [e10s-m6] → [e10s-m7]
Summary: Errors are thrown in the console while using Timeline in a e10s window → [e10s] Errors are thrown in the console while using Timeline in a e10s window
This bug shouldn't block e10s-m7, we don't have an STR
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.