Closed
Bug 1407766
Opened 7 years ago
Closed 7 years ago
Nightly 58 displays blank pages in the browser after Symantec Endpoint is installed
Categories
(Core :: Security: Process Sandboxing, defect, P1)
Tracking
()
VERIFIED
FIXED
mozilla58
Tracking | Status | |
---|---|---|
firefox58 | --- | fixed |
People
(Reporter: nils, Assigned: jimm)
References
()
Details
Attachments
(1 file)
1.13 KB,
patch
|
bobowen
:
review+
|
Details | Diff | Splinter Review |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0 Build ID: 20171009192146 Steps to reproduce: After installing Symantec Endpoint Protection on Windows 10, browser only displays blank pages in tabs. Local start page will not load. Dev Edition in the 57 branch appears to be unaffected by this. Actual results: Nothing displays within the browser, only white blank space. Expected results: Load pages normally.
Comment 1•7 years ago
|
||
Can you set the |security.sandbox.content.level| preference to 3, restart the browser, and let us know if this still happens? (The default value is 4 on nightly)
about:config page will not load to allow me to make any changes.
Comment 3•7 years ago
|
||
Ouch. Ok, let's try this a different way, can you try starting firefox with the environment variable |MOZ_DISABLE_CONTENT_SANDBOX| set to 1?
Same situation here. MOZ_DISABLE_CONTENT_SANDBOX=1 allows me to run nightly. Then I changed security.sandbox.content.level to 3, restarted nightly (without setting MOZ_DISABLE_CONTENT_SANDBOX to 1) and same problem appears (all pages are blank). Nightly version: 58.0a1 (2017-10-11) (64-bit) Built from https://hg.mozilla.org/mozilla-central/rev/20d9ad08dd36fe5230ad0ccf6cb3e4865d7851cf
Assignee | ||
Comment 5•7 years ago
|
||
Hey tracy, there's a trial of this av [1], would you please attempt to reproduce, and if so, find a regression range in 58. [1] https://www.symantec.com/products/endpoint-protection
Flags: needinfo?(twalker)
Assignee | ||
Updated•7 years ago
|
OS: Unspecified → Windows
Priority: -- → P1
Hardware: Unspecified → All
Assignee | ||
Comment 6•7 years ago
|
||
I wonder if this is a regression from bug 1406068. Can someone who can reproduce try a nightly build prior to 10-10?
Assignee | ||
Comment 7•7 years ago
|
||
nightly for testing: http://ftp.mozilla.org/pub/firefox/nightly/2017/10/2017-10-09-10-01-34-mozilla-central/
Assignee | ||
Comment 8•7 years ago
|
||
Lets pull these just to be safe.
Attachment #8917598 -
Flags: review?(bobowencode)
Assignee | ||
Updated•7 years ago
|
Attachment #8917598 -
Attachment is patch: true
I have the same problem and reverted to 2017-09-09. Cannot reproduce on 2017-09-09 build. Also https://bugzilla.mozilla.org/show_bug.cgi?id=1403912 seems the same issue but for a different AV product?
Updated•7 years ago
|
Attachment #8917598 -
Flags: review?(bobowencode) → review+
Comment 10•7 years ago
|
||
Pushed by bobowencode@gmail.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/381e276f3534 Remove symantec dlls from the content process dll blocklist due to process startup issues associated with symantec av products. r=bobowen
Assignee | ||
Updated•7 years ago
|
Reporter | ||
Comment 11•7 years ago
|
||
(In reply to Igor M. from comment #4) > Same situation here. MOZ_DISABLE_CONTENT_SANDBOX=1 allows me to run nightly. > Then I changed security.sandbox.content.level to 3, restarted nightly > (without setting MOZ_DISABLE_CONTENT_SANDBOX to 1) and same problem appears > (all pages are blank). > > Nightly version: 58.0a1 (2017-10-11) (64-bit) > Built from > https://hg.mozilla.org/mozilla-central/rev/ > 20d9ad08dd36fe5230ad0ccf6cb3e4865d7851cf This is the same result that I saw with yesterday's build (2017-10-11).
Comment 12•7 years ago
|
||
Version 57a1 from 09-09 works fine. Same with version linked in Comment 7 (no problems). However, current nightly still has empty pages. security.sandbox.content.level 3 or 4 did not make any difference in all cases above.
Reporter | ||
Comment 13•7 years ago
|
||
Just updated to the 2017-10-12 build, and the issue is still occurring.
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → jmathies
Comment 14•7 years ago
|
||
Nils, Igor - thanks for checking, but this is still on mozilla-inbound, it should get merged to mozilla-central soon and then the next Nightly created after that will contain it.
Comment 15•7 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/381e276f3534
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
status-firefox58:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla58
Assignee | ||
Updated•7 years ago
|
Flags: needinfo?(twalker)
Comment 17•7 years ago
|
||
Nils, Igor - this change is now in the latest Nightly, it would be great if you would confirm that it fixes this issue.
Flags: needinfo?(nils)
Flags: needinfo?(igor.miletic)
Reporter | ||
Comment 18•7 years ago
|
||
Yes, this does fix the issue as I'm posting this via Nightly right now, build 2017-10-15. Thanks everyone!
Flags: needinfo?(nils)
Comment 19•7 years ago
|
||
Same here. Works well on the build 2017-10-15.
Flags: needinfo?(igor.miletic)
You need to log in
before you can comment on or make changes to this bug.
Description
•