Closed Bug 798495 Opened 12 years ago Closed 12 years ago

remove devtools sandbox running in b2g

Categories

(Firefox OS Graveyard :: General, defect, P1)

Product:
Firefox OS Graveyard
Component:
General
Type:
defect

Tracking

(blocking-basecamp:+)

Status:
RESOLVED WORKSFORME
Project Flags:
blocking-basecamp +

People

(Reporter: justin.lebar+bug, Assigned: ttaubert)

References

Details

(Whiteboard: [MemShrink:P2][slim:<1MB]) 

Along the same lines as bug 794228: It appears some devtools code is running in b2g:

├──19.30 MB (34.91%) -- js-non-window
│  ├──12.29 MB (22.24%) -- compartments
│  │  ├──11.22 MB (20.29%) -- non-window-global
[...]
│  │  │  └───0.61 MB (01.10%) ++ compartment([System Principal], [anonymous sandbox] (from: resource:///modules/devtools/dbg-server

Is this intentional?  If so, we need to remember to disable it in release builds.
If this is related to marionette, then it should be off unless explicitly enabled.
Blocks: slim-fast
blocking-basecamp: --- → ?
Whiteboard: [MemShrink]
+dcamp

Will disabling this affect the remote debugger?
jhford has a bug in B2G (https://github.com/mozilla-b2g/B2G/issues/84) to allow us to disable Marionette except for eng builds.
The remote debugger shouldn't be affected by disabling marionette;  if you enable the remote debugger it will load the debugger server itself.

Cc'ing past to make sure I'm telling the truth.
Dave is right. Right now disabling marionette is actually a requirement for a working debugger (bug 764913).
blocking-basecamp: ? → +
Whiteboard: [MemShrink] → [MemShrink][slim:<1MB]
Whiteboard: [MemShrink][slim:<1MB] → [MemShrink:P2][slim:<1MB]
Josh - Assigning to you to see if you can help out with this one. If not, feel free to reassing to nobody.
Assignee: nobody → josh
Priority: -- → P1
Summary: devtools sandbox running in b2g → remove devtools sandbox running in b2g
I will defer until I can actually dedicate time to it.
Assignee: josh → nobody
Let's see if Tim can give it a try.
Assignee: nobody → ttaubert
I'm pretty sure this has been fixed by bug 779984. The sandbox doesn't seem to exist in user builds. Can anyone confirm?
Status: NEW → ASSIGNED
I don't see any memory used by a dbg-server compartment in a user build.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.