Expose "Dynamic analysis of chrome->content" as an XPCOM service

NEW
Unassigned

Status

()

Core
General
7 years ago
7 years ago

People

(Reporter: Honza, Unassigned)

Tracking

(Depends on: 1 bug)

Trunk
x86
Windows Vista
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

7 years ago
In order to prepare a plan for Firebug transition to e10s we want to utilize a logging-feature introduced in bug 666713 (Dynamic analysis of chrome->content operations in Firefox) and identify all places in Firebug where chrome touches the content. 

As expected, I am getting huge log file. Only starting Firefox and reloading the home page produces: 4MB, 60K+ lines

I would like to redirect the logging into Firebug Tracing Console that we also use to see all logs coming from Firebug itself (often the only way how to debug a debugger).

Would it be possible to expose a simple XPCOM (service) that Firebug could access in JS, register a listener into it and handle all logs dynamically?

The listener could get following parameters:

function contentAccessListener(accessDesc, jscontext, object, property, stack)
{
}

Honza
(Reporter)

Updated

7 years ago
Depends on: 666713

Comment 1

7 years ago
We could, but I suspect that the logs aren't really going to be useful in the Firebug case. I think that's just going to involve straight-up engineering so that code which touches content is run in the correct process.
(Reporter)

Comment 2

7 years ago
(In reply to Benjamin Smedberg  [:bsmedberg] from comment #1)
> We could, but I suspect that the logs aren't really going to be useful in
> the Firebug case. I think that's just going to involve straight-up
> engineering so that code which touches content is run in the correct process.
Yes, but before we start refactoring of Firebug architecture it would be great to have an overview which could help us to prepare a better plan.

For example, we could adapt entire Firebug panel by panel and start with the simpler ones.

Honza
You need to log in before you can comment on or make changes to this bug.