Closed
Bug 1252201
Opened 8 years ago
Closed 8 years ago
Docshell leak on debug e10s on 3 responsive mode tests
Categories
(DevTools :: Responsive Design Mode, defect, P2)
DevTools
Responsive Design Mode
Tracking
(e10s-)
RESOLVED
WONTFIX
Tracking | Status | |
---|---|---|
e10s | - | --- |
People
(Reporter: ntim, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [btpp-fix-later])
Summary ------------------- These failures happen because they open 2 clients that connect to the server. Example failing try push (dt5 and dt7): https://treeherder.mozilla.org/#/jobs?repo=try&revision=af6ee87736fb The failure only happens on Windows 7 debug e10s. This bug is about fixing and re-enabling those tests on that platform. Failing tests ------------------- Responsive Mode: - browser_responsivecomputedview.js - browser_responsiveruleview.js Style Editor: - browser_styleeditor_media_sidebar_links.js
Reporter | ||
Updated•8 years ago
|
Blocks: dte10s, e10s-tests
See Also: → 1250058
Reporter | ||
Updated•8 years ago
|
Summary: Docshell leak on Windows 7 debug e10s for 3 responsive mode tests → Docshell leak on Windows 7 debug e10s on 3 responsive mode tests
Reporter | ||
Comment 1•8 years ago
|
||
For reference, the tests started failing after bug 828008.
I am guessing this is uncovering some latent issues with 2 clients, since that is mostly not covered by tests.
Priority: -- → P2
Whiteboard: [btpp-fix-later]
Updated•8 years ago
|
tracking-e10s:
--- → -
Comment 5•8 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/efefdfec4198
Comment 6•8 years ago
|
||
This affects debug e10s on all platforms.
Summary: Docshell leak on Windows 7 debug e10s on 3 responsive mode tests → Docshell leak on debug e10s on 3 responsive mode tests
Comment 8•8 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/9153b5be1ff0
These tests will be removed when old RDM is removed, so I don't think we care about this anymore.
Updated•6 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•