Make the debugger self-debuggable (create/delete profile...)

RESOLVED WONTFIX

Status

P3
normal
RESOLVED WONTFIX
7 years ago
5 months ago

People

(Reporter: vporof, Assigned: vporof)

Tracking

12 Branch

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [chrome-debug])

(Assignee)

Description

7 years ago
This may depend on a lot of stuff, so it's quite down in the [chrome-debug] priority queue.
Priority: -- → P3
One hacky way to do this is figure out if the process in which we are launching the chrome debugger from is a debugger process, and in that case (only!) create a profile with a random name. This is the approach we took in the remote-debug prototype.

Advantage: we don't need to wait for a removeProfile API (bug 738590).
Disadvantage: there are profile directories accumulating in the user's hard drive, but at least this will only be a concern for people who try to debug a debugger, whom we could expect to be able to remove them manually.
(Assignee)

Comment 2

7 years ago
(In reply to Panos Astithas [:past] from comment #1)
> One hacky way to do this is figure out if the process in which we are
> launching the chrome debugger from is a debugger process, and in that case
> (only!) create a profile with a random name. This is the approach we took in
> the remote-debug prototype.
> 
> Advantage: we don't need to wait for a removeProfile API (bug 738590).
> Disadvantage: there are profile directories accumulating in the user's hard
> drive, but at least this will only be a concern for people who try to debug
> a debugger, whom we could expect to be able to remove them manually.

We don't need to worry about that anymore. The current approach of creating a remote debugger makes sure that when the new firefox instance is killed (or dies by it's own will), we delete the temporary profile (thank you nsIToolkitProfileService). We currently *don't* also delete the profile data in the profile dir (as there may be some user prefs set, etc. reasons) and the profile name isn't random (so we basically reuse the same disk space and prefs yay!). In the yodawg debugger case, we can completely remove the new profile, so we can safely give it a random name each time.
Was this bug only about the profile handling? Should we WONTFIX it?
(Assignee)

Comment 4

6 years ago
(In reply to Panos Astithas [:past] from comment #3)
> Was this bug only about the profile handling? Should we WONTFIX it?

It was about profiles and *any other stuff that we may encounter, aka ...*, but I can't think of anything from the top of my head that needs to be done that is not in a different bug already. Let's WONTFIX this and file a new bug if there's a need for that in the future.
Status: ASSIGNED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → WONTFIX

Updated

5 months ago
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.