FLAM® Issue Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000962FL51.1 FLCLpublic2019-02-28 17:512019-12-05 10:47
ReporterFalk Reichbott 
Assigned ToFalk Reichbott 
PriorityhighSeveritymajorReproducibilitysometimes
StatusassignedResolutionopen 
PlatformGeneralOSGeneralOS VersionGeneral
Product Version5.1.19 
Target Version5.1.26Fixed in Version 
Summary0000962: Limit the maximal internal block size to prevent memory exhausting through expansion at decompression
DescriptionCurrently FLAM works block by block. If you read a block with 64 KiB (default) a maximal expansion of GZIP by factor 900 can result in 1 GiB memory allocation by FLAM to handle the extracted block in memory. For a secure production environment the maximal allocated memory must be limited. In such case we need a solution, where only a part of the original block is extracted so that anything fit in the maximal block size. The default could by at factor 4 of the given block size.
TagsNo tags attached.
Attached Files

- Relationships

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2019-02-28 17:51 Falk Reichbott New Issue
2019-02-28 17:51 Falk Reichbott Status new => assigned
2019-02-28 17:51 Falk Reichbott Assigned To => Falk Reichbott
2019-06-19 19:37 Falk Reichbott Target Version 5.1.21 => 5.1.22
2019-12-05 10:37 Falk Reichbott Target Version 5.1.22 => 5.1.27
2019-12-05 10:47 Falk Reichbott Target Version 5.1.27 => 5.1.26


Copyright © 2000 - 2020 MantisBT Team
Powered by Mantis Bugtracker