Details
-
Bug
-
Resolution: Fixed
-
P3: Somewhat important
-
5.15, 6.4.2
-
None
-
79abdd3cd (dev), d117cd5f3 (6.6), 022657d7d (dev), 813bbc515 (dev), acc2cdb6c (6.6), 4a15c6bdf (6.6)
Description
Quoting QTBUG-112200, which has a reproducer for this issue, but was fixed in a different way:
I debugged the problem and found that QStyleHelper::uniqueName in QFusionStyle::qt_fusion_draw_arrow always gives different values on same objects. This is caused by palette.cacheKey() (only if our own stylesheet is used).
uniqueName() returning a different value every time should be fixed, too, because it makes the pixmap caching basically non-existent.
I've micro-optimized the painting, but it's of course still orders of magnitudes slower than blitting a cached pixmap.
Attachments
Issue Links
- split from
-
QTBUG-112200 Possible memory leak with Fusion style
- Closed
For Gerrit Dashboard: QTBUG-114473 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
486629,7 | QStyle: don't use the QPixmapCache when a style sheet is set | dev | qt/qtbase | Status: MERGED | +2 | 0 |
489002,3 | QPixmapCache: ignore insertion or searches with empty key | dev | qt/qtbase | Status: MERGED | +2 | 0 |
489003,4 | Refactor QStyle: const'ify some local variables | dev | qt/qtbase | Status: MERGED | +2 | 0 |
489091,2 | QPixmapCache: ignore insertion or searches with empty key | 6.6 | qt/qtbase | Status: MERGED | +2 | 0 |
490614,2 | QStyle: don't use the QPixmapCache when a style sheet is set | 6.6 | qt/qtbase | Status: MERGED | +2 | 0 |
490615,2 | Refactor QStyle: const'ify some local variables | 6.6 | qt/qtbase | Status: MERGED | +2 | 0 |