Closed
Bug 1209215
Opened 9 years ago
Closed 9 years ago
[e10s] View source fails to work with dom.ipc.processCount=4
Categories
(Toolkit :: View Source, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1165309
People
(Reporter: dsmith, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 Firefox/43.0 Build ID: 20150928004020 Steps to reproduce: Attempted to use view source from the context menu. Actual results: When attempting to view source (since the change to put it in a tab instead of a separate window), about 90% of the time nothing is loaded. The tab is blank, and nothing is in the address bar. Most of the time that it does work, it is the very first attempt to view source in a session; all subsequent attempts fail. Restarting with addons disabled had no effect. Restarting with Electrolysis disabled (and addons enabled) allowed view source to work 100% of the time. Starting with a new temp profile always had view source work. This profile was rebuilt from scratch just a couple months ago (July 14). Expected results: View source should always show the source code of the page.
I tried with Nightly and it works. Maybe still bugged in DE. Could you test in Nightly, please.
Reporter | ||
Comment 2•9 years ago
|
||
Installed Nightly: 20150928030206 Copied Profile for testing Same behavior. Reviewed modified profile settings, and was reminded of a potential consideration: process count. I'd had the dom.ipc.processCount value set to 4. Changing that back to 1 allowed the view source to work properly. Creating a new temp profile, and setting the ipc count to 4 caused the view source to stop working. So that's where the issue seems to step from.
Flags: needinfo?(dsmith)
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: View source fails to work when Electrolysis is active → [e10s] View source fails to work with dom.ipc.processCount=4
tracking-e10s:
--- → ?
I believe this is the same as bug 1165309. Feel free to reopen if not.
You need to log in
before you can comment on or make changes to this bug.
Description
•