1berry/qtbase
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Image IO: increase the default allocation limit

Browse Source 
Time passes, Moore's law is working.

As a drive-by, make the doc more informative.

Fixes: QTBUG-113637
Pick-to: 6.5
Change-Id: Ic388b8850ace02c429d4d8175d31db86912d3afe
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@qt.io>
This commit is contained in:
Eirik Aavitsland 2023-05-22 13:23:46 +02:00
parent 8d11e05f8f
commit 2385d66923
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
src/gui/image/qimagereader.cpp
View File

@ -463,7 +463,7 @@ public:
static int maxAlloc; static int maxAlloc;
}; };
int QImageReaderPrivate::maxAlloc = 128; // 128 MB is enough for an 8K 32bpp image int QImageReaderPrivate::maxAlloc = 256; // 256 MB is enough for an 8K 64bpp image
/*! /*!
\internal \internal
@ -1572,6 +1572,8 @@ int QImageReader::allocationLimit()
loading corrupt image files. It is normally not needed to change it. The loading corrupt image files. It is normally not needed to change it. The
default limit is large enough for all commonly used image sizes. default limit is large enough for all commonly used image sizes.
At runtime, this value may be overridden by the environment variable \c QT_IMAGEIO_MAXALLOC.
\note The memory requirements are calculated for a minimum of 32 bits per pixel, since Qt will \note The memory requirements are calculated for a minimum of 32 bits per pixel, since Qt will
typically convert an image to that depth when it is used in GUI. This means that the effective typically convert an image to that depth when it is used in GUI. This means that the effective
allocation limit is significantly smaller than \a mbLimit when reading 1 bpp and 8 bpp images. allocation limit is significantly smaller than \a mbLimit when reading 1 bpp and 8 bpp images.