Closed
Bug 1057519
Opened 10 years ago
Closed 9 years ago
ghost windows in parent process with washingtonpost.com
Categories
(Core :: DOM: Content Processes, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: bkelly, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [MemShrink:P2])
Attachments
(1 file)
|
(deleted),
application/gzip
|
Details |
I see ghost windows that won't go away after I minimize memory while dogfooding e10s. See attached memory report.
I have CC/GC logs as well, but they are 78MB compressed so I can't upload them here. If needed I can upload them to dropbox or something.
It appears this is mostly one site, washingtonpost.com, so not sure if its a site issue or an e10s issue.
|
||
Updated•10 years ago
|
tracking-e10s:
--- → ?
|
||
Updated•10 years ago
|
|
||
Updated•10 years ago
|
Whiteboard: [MemShrink] → [MemShrink:P2]
|
Reporter | |
Comment 1•10 years ago
|
||
I just saw this happen with non-e10s. It was washingtonpost.com again.
tracking-e10s:
+ → ---
Summary: [e10s] ghost windows in parent process with e10s desktop → ghost windows in parent process with washingtonpost.com
You're probably seeing bug 1061202 if you see it in non-e10s.
|
|
||
Comment 3•9 years ago
|
||
washingtonpost.com is my go-to site for creating ghost windows, but hopefully you aren't seeing any at the moment...
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
|
|
||
Updated•9 years ago
|
Blocks: GhostWindows
You need to log in
before you can comment on or make changes to this bug.
Description
•