High consumption: Seen on Win10 and Linux x64.
Out of memory: on Linux i586.
263b29eedb223dec1ecaee193302070af87a1852 (qt/qtbase/dev) 6485b6d45ad165cf976138cf8ab683c42515e794 (qt/qtbase/5.15)
Since Qt5.15, lconvert uses several gigabytes of memory to translate an (admittedly large) file of about 15.000 string entries. The .po files are about 2.5MB, translated .qm about 1MB, nothing which I consider scary. In between, a single lconvert process was reported to use 2.5GB of RAM. Now translate on 4 or more cores...
This new behaviour suddenly causes slow (allocation to virtual memory on 8/12GB PCs!) or even failed builds (out of memory) on CI systems.
Are there any hidden limits for the tools?
|For Gerrit Dashboard: QTBUG-87010|
|317211,7||Fix allocated memory of QByteArray returned by QIODevice::readLine||dev||qt/qtbase||Status: MERGED||+2||0|
|317907,3||Fix allocated memory of QByteArray returned by QIODevice::readLine||5.15||qt/qtbase||Status: MERGED||+2||0|