Loading...
Loading...
Buffering without constraint by INFLATE can lead to low memory conditions and/or memory fragmentation. This in conjunction with other allocator behaviors can lead to allocation failures and/or SIGABRT failures.
We might run into low memory conditions and/or memory fragmentation. This in conjunction with other allocator behaviors can lead to allocation failures and/or SIGABRT failures.
When large transfers of compressed response documents are ongoing, INFLATE will buffer all ingress regardless of how fast the inflation is progressing or not. When subjected to concurrent large compressed response documents, zlib becomes throttled thus causing INFLATE jobs to proceed slowly. This causes the ingress pouring in to INFLATE to be buffered. Note that some modules, such as REWRITE, make heavy use of INFLATE, which makes those modules particularly susceptible to this issue.
None
Flow control is added to INFLATE, which would limit the amount of data buffered by the module.
Click on a version to see all relevant bugs
F5 Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.