https://bugs.kde.org/show_bug.cgi?id=487043
--- Comment #16 from Fabian Vogt <fab...@ritter-vogt.de> --- (In reply to Méven Car from comment #15) > (In reply to Fabian Vogt from comment #14) > > Apparently something in Qt's Rhi has a lock file in .cache which needs to be > > synced to disk > > (/home/testuser/.cache/kwin/qtpipelinecache-x86_64-little_endian-lp64/ > > qqpc_opengl.lck). Fortunately it's only a fdatasync and not a fsync or even > > sync so it only waits until that specific file data has made it to disk, but > > it can still block for a while. > > > > Maybe there's a way to avoid QLockFile use there. > > Relevant documentation: > https://doc.qt.io/qt-5/qmldiskcache.html > > Another workaround would be to use `export > QML_DISK_CACHE_PATH=/tmp/qmlcache` where /tmp/qmlcache is a fast drive or a > ramdisk. > > For some reason (that I don't know but there is probably one) we don't use > `qt_add_qml_module` in plasma and kwin, that does pre-compile the > js/qml/C++-binding and embedded it in the executable resources: > https://doc.qt.io/qt-6/qt-add-qml-module.html#caching-compiled-qml-sources > > We do use it in applications (spectacle, neochat...). The QML disk cache is completely unrelated. This is the Qt Rhi pipeline cache, which is (unconditionally) enabled by QtQuick: https://github.com/qt/qtdeclarative/blob/d9ceacd4126ff48d5f1e6d5b7b0f3be426d2cf35/src/quick/scenegraph/qsgrhisupport.cpp#L941 -- You are receiving this mail because: You are watching all bug changes.
