Details
-
Bug
-
Resolution: Done
-
P1: Critical
-
5.15.1
-
None
-
Linux/Wayland
-
ef763e195892a6d8ce207f5d947fe508f645cb6d (qt/qtbase/dev) c67eaed8468c36629597aead9a768c9fe711ad85 (qt/qtbase/6.0) 9807573764bea70d1e449881c5fb67fc262ca8c4 (qt/qtbase/6.1) 6a64b8ed56d70d76cc154e66f03824b3c3a2a786 (qt/tqtc-qtbase/tqtc/lts-5.15)
Description
We try to render texts in an OpenGL application. For this we assemble the text glyph by glyph using QRawFont.
On Debian Buster we get wrong results: The resulting QImage contains the correct glyph but is followed by lots of garbage.
On Windows the result seems to be correct.
See screenshots.
You may reproduce the effect using the attached code.
With real world code with whole texts instead of only a single glyph this leads to crashes, probably because of memory corruption.
Attachments
| For Gerrit Dashboard: QTBUG-90236 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 332939,3 | Fix crash when requesting A32 glyph on Wayland | dev | qt/qtbase | Status: MERGED | +2 | 0 |
| 333028,2 | Fix crash when requesting A32 glyph on Wayland | 6.1 | qt/qtbase | Status: MERGED | +2 | 0 |
| 333029,2 | Fix crash when requesting A32 glyph on Wayland | 6.0 | qt/qtbase | Status: MERGED | +2 | 0 |
| 333030,3 | Fix crash when requesting A32 glyph on Wayland | tqtc/lts-5.15 | qt/tqtc-qtbase | Status: MERGED | +2 | 0 |