Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
V
varnish-cache
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Commits
Open sidebar
varnishcache
varnish-cache
Commits
0945a8f4
Commit
0945a8f4
authored
Mar 11, 2019
by
Dridi Boukelmoune
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Mention another source of stack increase
parent
6f65045b
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
5 additions
and
1 deletion
+5
-1
changes-trunk.rst
doc/sphinx/whats-new/changes-trunk.rst
+5
-1
No files found.
doc/sphinx/whats-new/changes-trunk.rst
View file @
0945a8f4
...
...
@@ -46,7 +46,11 @@ external libraries that are not under control of the Varnish project
(such as glibc). This may also have been related to stack overflow
issues on some platforms when recent versions of `jemalloc`_, the
recommended memory allocator for Varnish, have been used together with
`pcre`_ with JIT compilation enabled.
`pcre`_ with JIT compilation enabled. Compiler hardening flags may
also increase stack usage and on some systems such stack protector
flags may be enabled by default. With the addition of new mitigations
to new compiler releases, stack consumption may also increase on that
front.
Tests have shown that Varnish runs stably with the new default stack
size on a number of platforms, under conditions that previously may
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment