| commit | c130f03c1c7d4092c900273da0c7088e014d1a52 | |
| author | mdempsky@chromium.org <mdempsky@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | |
| Thu, 1 May 2014 07:44:47 +0000 (1 07:44 +0000) | ||
| committer | mdempsky@chromium.org <mdempsky@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | |
| Thu, 1 May 2014 07:44:47 +0000 (1 07:44 +0000) | ||
| tree | bad72181b5767f9e4529d5616372115248798aae | treesnapshot (tar.gz zip) |
| parent | 67816389fdc7cd061a66593da295ffc2d8062082 | commitdiff |
RenderFrameImpl: don't call DumpWithoutCrashing() on Linux
Contrary to its name, DumpWithoutCrashing() will always crash when
called from a Linux renderer process when breakpad and sandboxing are
enabled. Fixing this will require changes to breakpad and possibly
the seccomp-bpf sandbox, so for the time being stop the crash server
from getting flooded with useless stack traces.
BUG=349600
Review URL: https://codereview.chromium.org/263743003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@267466 0039d316-1c4b-4281-b951-d872f2087c98
Contrary to its name, DumpWithoutCrashing() will always crash when
called from a Linux renderer process when breakpad and sandboxing are
enabled. Fixing this will require changes to breakpad and possibly
the seccomp-bpf sandbox, so for the time being stop the crash server
from getting flooded with useless stack traces.
BUG=349600
Review URL: https://codereview.chromium.org/263743003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@267466 0039d316-1c4b-4281-b951-d872f2087c98
| content/renderer/render_frame_impl.cc | diffblobblamehistory |