https://bugs.kde.org/show_bug.cgi?id=401940
Sharaf <sharafzaz...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap
|hics/krita/commit/b57713c24 |hics/krita/commit/01514224c
|454c78d1a54e3f8fa0526484ba8 |c4558d94c67eb2b8e9feeabec8a
|19d3 |b89c
--- Comment #29 from Sharaf <sharafzaz...@gmail.com> ---
Git commit 01514224cc4558d94c67eb2b8e9feeabec8ab89c by Sharaf Zaman.
Committed on 08/06/2021 at 07:26.
Pushed by szaman into branch 'krita/4.4.5'.
Bugfix: Artifact with more than one active assitant
Problem: With more than one assitants active on canvas, often on devices
with high resolution the Pixmap cache would fill up immediately. This
would internally trigger glDeleteTexture right after the first pixmap is
rendered and when turn for second pixmap is due, it would get assigned
the same name as the previously generated (which is a correct behavior!
but it only seems to happen with some drivers). With same name as
previous one Qt doesn't render it (see
QOpenGL2PaintEngineExPrivate::updateTexture).
Workaround: Because of this name clash, we workaround this Qt bug by
increasing the cache size, so the new textures don't immediately delete
the previous ones and take their names. Ideally, this should be fixed
inside Qt.
Devices with this problem:
+ Android
+ ChromeOS (mesa)
+ Windows (ANGLE)
M +7 -4 libs/ui/opengl/kis_opengl.cpp
https://invent.kde.org/graphics/krita/commit/01514224cc4558d94c67eb2b8e9feeabec8ab89c
--
You are receiving this mail because:
You are watching all bug changes.
