Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Remove or fix the "Running without renderer sandbox" error message #22

Closed
probablycorey opened this issue Jun 11, 2013 · 2 comments
Closed

Remove or fix the "Running without renderer sandbox" error message #22

probablycorey opened this issue Jun 11, 2013 · 2 comments
Labels
enhancement ✨

Comments

@probablycorey
Copy link

Do you know why this error always is logged?

[0611/105852:ERROR:renderer_main.cc(212)] Running without renderer sandbox

This has been logged since we started using CEF1 a long time ago. It is not a huge problem, and I don't think we should spend a huge amount of time on it, but it has always annoyed me.
@zcbenz
Copy link
Member

zcbenz commented Jun 12, 2013

It's showed because the renderer sandbox is disabled, otherwise many node functions won't work. It is in fact not a error message, but a kind warning. Removing it only needs a one line patch for chromium.

But I want to keep this message so I can know whether and when the renderer has started, it's helpful for debugging. How about replacing it with a warmer message? like:

[0611/105852:INFO:renderer_main.cc(212)] Renderer started without sandbox

@probablycorey
Copy link
Author

If it is helpful to you let's just keep it!

@zcbenz zcbenz closed this as completed in a8eaaf9 Jun 19, 2013
@d4k0 d4k0 mentioned this issue Mar 9, 2015
Closed
@ladenberger ladenberger mentioned this issue Jan 15, 2016
Closed
@curcuz curcuz mentioned this issue May 26, 2016
Closed
@tejohnso tejohnso mentioned this issue Jun 13, 2016
Closed
@ns ns mentioned this issue Feb 6, 2017
Closed
kevinsawicki pushed a commit that referenced this issue May 9, 2017
@zcbenz
Use abusolute path when linking to external libraries. Fixes #22.
fdd2bb7 
The ninja generator of gyp behaves strangely on the 'libraries' field of link
settings, for example, specifying path to an external library works well on
both xcodebuild and msvc generators, but the ninja generator would link to
the wrong path (it can neither translate relative path correctly, nor convert
the command line parameter to the '-lxxx' form).

The only way to make all generators work on all platforms is to use abusolute
paths for external libraries.
kevinsawicki pushed a commit that referenced this issue May 9, 2017
@aroben
Update libchromiumcontent to get ICU headers
823aece 
* vendor/libchromiumcontent ee4cea0...33472d4 (5):
  > Export ICU headers
  > When `gclient sync` fails, revert all local changes and try again
  > Merge pull request #23 from brightray/chromiumviews_pdb
  > Merge pull request #22 from brightray/cygwin2
  > Update to Chrome 28.0.1500.71
kevinsawicki pushed a commit that referenced this issue May 9, 2017
@zcbenz
Use abusolute path when linking to external libraries. Fixes #22.
5e807cf 
The ninja generator of gyp behaves strangely on the 'libraries' field of link
settings, for example, specifying path to an external library works well on
both xcodebuild and msvc generators, but the ninja generator would link to
the wrong path (it can neither translate relative path correctly, nor convert
the command line parameter to the '-lxxx' form).

The only way to make all generators work on all platforms is to use abusolute
paths for external libraries.
kevinsawicki pushed a commit that referenced this issue May 9, 2017
@aroben
Update libchromiumcontent to get ICU headers
d32a2fb 
* vendor/libchromiumcontent ee4cea0...33472d4 (5):
  > Export ICU headers
  > When `gclient sync` fails, revert all local changes and try again
  > Merge pull request #23 from brightray/chromiumviews_pdb
  > Merge pull request #22 from brightray/cygwin2
  > Update to Chrome 28.0.1500.71
@avengerweb avengerweb mentioned this issue Oct 13, 2017
Closed
@ClarkWang-2013 ClarkWang-2013 mentioned this issue Nov 23, 2017
Merged
@ckerr ckerr mentioned this issue Oct 24, 2018
Closed
This was referenced Oct 27, 2020
Merged
Merged
Merged
This was referenced Nov 19, 2021
Merged
Merged
Merged
Closed
@nopandcc nopandcc mentioned this issue Mar 23, 2022
Closed
3 tasks
This was referenced Jun 1, 2023
Merged
Merged
Merged
This was referenced Aug 16, 2023
Merged
Merged
Closed
@wujinli wujinli mentioned this issue Jan 31, 2024
Merged
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement ✨
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@probablycorey @zcbenz