# QThreadStorage warning in the log **URL:** \ **Category:** Help\ **Tags:** qt\ **Created:** [February 4, 2025, 5:40pm UTC](https://discuss.kde.org/t/qthreadstorage-warning-in-the-log/29264 "2025-02-04T17:40:43Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![Guido\_I](https://discuss-cdn.kde.org/user_avatar/discuss.kde.org/guido_i/32/2430_2.png) [@Guido\_I](https://discuss.kde.org/u/Guido_I)\ **Post date:** [February 4, 2025, 5:40pm UTC](https://discuss.kde.org/t/qthreadstorage-warning-in-the-log/29264/1 "2025-02-04T17:40:43Z")
I would like to report the bug but I do not know in which component. Practically every KDE application leaves a similar message in the log `QThreadStorage: Thread 0x61e8d47d67a0 exited after QThreadStorage 9 destroyed` here are a few examples | 04.02.2025 18:23:06:941 | kdeconnectd | QThreadStorage: Thread 0x5c4e47a16b50 exited after QThreadStorage 8 destroyed | | --- | --- | --- | | 04.02.2025 18:23:06:941 | kdeconnectd | QThreadStorage: Thread 0x5c4e47a16b50 exited after QThreadStorage 7 destroyed | | 04.02.2025 18:23:06:941 | kdeconnectd | QThreadStorage: Thread 0x5c4e47a16b50 exited after QThreadStorage 6 destroyed | | 04.02.2025 18:23:06:941 | kdeconnectd | QThreadStorage: Thread 0x5c4e47a16b50 exited after QThreadStorage 2 destroyed | | 04.02.2025 18:24:48:959 | dolphin | QThreadStorage: Thread 0x62067d9841d0 exited after QThreadStorage 9 destroyed | | 04.02.2025 18:25:34:595 | konsole | QThreadStorage: Thread 0x5dbefabaf6a0 exited after QThreadStorage 9 destroyed | | 04.02.2025 18:25:57:326 | kcalc | QThreadStorage: Thread 0x5a5fe0125d40 exited after QThreadStorage 8 destroyed | | 04.02.2025 18:28:52:878 | spectacle | QThreadStorage: Thread 0x61e8d47d67a0 exited after QThreadStorage 9 destroyed | | 04.02.2025 18:31:31:729 | kioworker | QThreadStorage: Thread 0x61010e5c4600 exited after QThreadStorage 8 destroyed | | 04.02.2025 18:31:31:730 | kioworker | QThreadStorage: Thread 0x61010e5c4600 exited after QThreadStorage 7 destroyed | | 04.02.2025 18:31:31:730 | kioworker | QThreadStorage: Thread 0x61010e5c4600 exited after QThreadStorage 6 destroyed | | 04.02.2025 18:31:31:730 | kioworker | QThreadStorage: Thread 0x61010e5c4600 exited after QThreadStorage 1 destroyed | | 04.02.2025 18:31:33:082 | dolphin | QThreadStorage: Thread 0x58cec8b001d0 exited after QThreadStorage 9 destroyed | | 04.02.2025 18:31:57:204 | dragon | QThreadStorage: Thread 0x5c9b59aa6870 exited after QThreadStorage 8 destroyed | | 04.02.2025 18:36:31:696 | kdenlive | QThreadStorage: Thread 0x5fdba02f4510 exited after QThreadStorage 9 destroyed | However, QT but not KDE apps do not. Among those that do not: Octopi (pacman QT interface on Arch) Krita but also Systemsettings e Ksyslog which are KDE anyway Any idea? However, there do not seem to be any malfunctions. Moreover, if I launch them from the terminal, many more appear in the terminal itself, this is dolphin: ```auto QThreadStorage: Thread 0x60d8ff457600 exited after QThreadStorage 8 destroyed QThreadStorage: Thread 0x60d8ff457600 exited after QThreadStorage 7 destroyed QThreadStorage: Thread 0x60d8ff457600 exited after QThreadStorage 6 destroyed QThreadStorage: Thread 0x60d8ff457600 exited after QThreadStorage 1 destroyed QThreadStorage: Thread 0x6487b7bf11d0 exited after QThreadStorage 9 destroyed ``` ---
**Author:** ![Franken14679](https://discuss-cdn.kde.org/user_avatar/discuss.kde.org/franken14679/32/2497_2.png) [@Franken14679](https://discuss.kde.org/u/Franken14679)\ **Post date:** [February 6, 2025, 4:09pm UTC](https://discuss.kde.org/t/qthreadstorage-warning-in-the-log/29264/2 "2025-02-06T16:09:01Z")
@Guido_I: There’s also the following KDE Discuss thread – \<[KRunner - QThreadStorage](https://discuss.kde.org/t/krunner-qthreadstorage-thread-0x613719c95030-exited-after-qthreadstorage-8-destroyed/29223)\> And, there’s also a related Bug Report: \<[KRunner does not appear QThreadStorage](https://bugs.kde.org/show_bug.cgi?id=499477)\> * * * Looking at the Bug Report, it seems to be a Plasma 6 issue but, on this Plasma 5 system I’m seeing the following systemd user Journal entries – ```auto Feb 05 16:10:15 digikam[5072]: QThreadStorage: Thread 0x555d6cd94c70 exited after QThreadStorage 15 destroyed Feb 05 16:10:15 digikam[5072]: QThreadStorage: Thread 0x555d6cd94c70 exited after QThreadStorage 12 destroyed Feb 05 16:10:15 digikam[5072]: QThreadStorage: Thread 0x555d6ce3f3f0 exited after QThreadStorage 15 destroyed Feb 05 16:10:15 digikam[5072]: QThreadStorage: Thread 0x555d6ce3f3f0 exited after QThreadStorage 12 destroyed Feb 05 16:10:15 digikam[5072]: QThreadStorage: Thread 0x555d70f18220 exited after QThreadStorage 15 destroyed Feb 05 16:10:15 digikam[5072]: QThreadStorage: Thread 0x555d70f18220 exited after QThreadStorage 12 destroyed ``` ```auto Operating System: openSUSE Leap 15.6 KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 Kernel Version: 6.4.0-150600.23.33-default (64-bit) Graphics Platform: X11 Processors: 8 × AMD Ryzen 5 3400G with Radeon Vega Graphics Memory: 29.3 GiB of RAM Graphics Processor: AMD Radeon Vega 11 Graphics Manufacturer: ASUS ``` On this Qt5 system, only digiKam is throwing these messages. ---
**Author:** ![meven](https://discuss-cdn.kde.org/user_avatar/discuss.kde.org/meven/32/1748_2.png) [@meven](https://discuss.kde.org/u/meven)\ **Post date:** [February 6, 2025, 4:44pm UTC](https://discuss.kde.org/t/qthreadstorage-warning-in-the-log/29264/3 "2025-02-06T16:44:26Z")
It is a regression in Qt 6.8.2, reported and fixed in 6.8.3 with requests to backport the fix to ditros: [https://bugreports.qt.io/browse/QTBUG-133206](https://bugreports.qt.io/browse/QTBUG-133206) [https://bugreports.qt.io/browse/QTBUG-133500](https://bugreports.qt.io/browse/QTBUG-133500) [https://bugs.kde.org/show\_bug.cgi?id=499537](https://bugs.kde.org/show_bug.cgi?id=499537) ---
**Author:** ![meven](https://discuss-cdn.kde.org/user_avatar/discuss.kde.org/meven/32/1748_2.png) [@meven](https://discuss.kde.org/u/meven)\ **Post date:** [February 6, 2025, 4:50pm UTC](https://discuss.kde.org/t/qthreadstorage-warning-in-the-log/29264/4 "2025-02-06T16:50:29Z")
> [@Guido\_I](#): > > I would like to report the bug but I do not know in which component. We have [bugs.kde.org](http://bugs.kde.org) for this. If you don’t know the component pick a default one, if it concerns the session plasma-desktop, graphics kwin, file-management dolphin… And the bug should get triaged eventually. Although discuss can be an antichamber, in any case looking searching at recent bugs in [bugs.kde.org](http://bugs.kde.org) is a good idea to see if something is already reported. ---
**Author:** ![Guido\_I](https://discuss-cdn.kde.org/user_avatar/discuss.kde.org/guido_i/32/2430_2.png) [@Guido\_I](https://discuss.kde.org/u/Guido_I)\ **Post date:** [February 6, 2025, 5:07pm UTC](https://discuss.kde.org/t/qthreadstorage-warning-in-the-log/29264/5 "2025-02-06T17:07:26Z")
I know where the bugs are reported, but I wasn’t sure which component to use. Anyway, it seems to be a problem with Qt 6.8.2 ---
**Author:** ![BlueUSA](https://discuss-cdn.kde.org/letter_avatar_proxy/v4/letter/b/9dc877/32.png) [@BlueUSA](https://discuss.kde.org/u/BlueUSA)\ **Post date:** [February 6, 2025, 10:21pm UTC](https://discuss.kde.org/t/qthreadstorage-warning-in-the-log/29264/6 "2025-02-06T22:21:42Z")
> [@KRunner - QThreadStorage: Thread 0x613719c95030 exited after QThreadStorage 8 destroyed](https://discuss.kde.org/t/krunner-qthreadstorage-thread-0x613719c95030-exited-after-qthreadstorage-8-destroyed/29223): > > As we all know for some reason from Plasma 6.0 forward KRunner likes to stop working. Normally one just launches Konsole and enters krunner once or twice to get it running again. I just attempted that and I get the below. Any Ideas on what’s going on?  krunner  heavy_check_mark  11:48:44 AM QThreadStorage: Thread 0x613719c95030 exited after QThreadStorage 8 destroyed QThreadStorage: Thread 0x613719c95030 exited after QTh… ---
**Author:** ![mariol](https://discuss-cdn.kde.org/user_avatar/discuss.kde.org/mariol/32/1049_2.png) [@mariol](https://discuss.kde.org/u/mariol)\ **Post date:** [April 5, 2025, 2:14pm UTC](https://discuss.kde.org/t/qthreadstorage-warning-in-the-log/29264/7 "2025-04-05T14:14:17Z")
> [@KRunner - QThreadStorage: Thread 0x613719c95030 exited after QThreadStorage 8 destroyed](https://discuss.kde.org/t/krunner-qthreadstorage-thread-0x613719c95030-exited-after-qthreadstorage-8-destroyed/29223/12): > > Also on Kdeconnect-sms: [https://bugs.launchpad.net/ubuntu/+source/kdeconnect/+bug/2105767](https://bugs.launchpad.net/ubuntu/+source/kdeconnect/+bug/2105767) ---
**Author:** ![adiljaan](https://discuss-cdn.kde.org/letter_avatar_proxy/v4/letter/a/a4c791/32.png) [@adiljaan](https://discuss.kde.org/u/adiljaan)\ **Post date:** [April 14, 2025, 11:27am UTC](https://discuss.kde.org/t/qthreadstorage-warning-in-the-log/29264/8 "2025-04-14T11:27:48Z")
This problem persists in QT 6.8.3. Is there any other way to fix it? Every time I activate krunner, it also outputs the following message: ```auto qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x5d40b20de750 qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x5d40b20de750 ``` ---
**Author:** ![frc\_kde](https://discuss-cdn.kde.org/user_avatar/discuss.kde.org/frc_kde/32/8004_2.png) [@frc\_kde](https://discuss.kde.org/u/frc_kde)\ **Post date:** [May 28, 2025, 6:06pm UTC](https://discuss.kde.org/t/qthreadstorage-warning-in-the-log/29264/9 "2025-05-28T18:06:36Z")
I have seen it for the first time, now: ```auto $ spectacle --help (......) QThreadStorage: entry 9 destroyed before end of thread 0x5f2f182a6c50 QThreadStorage: entry 5 destroyed before end of thread 0x5f2f182a6c50 QThreadStorage: entry 4 destroyed before end of thread 0x5f2f182a6c50 ``` My system: ```auto $ kinfo Operating System: Arch Linux KDE Plasma Version: 6.3.5 KDE Frameworks Version: 6.14.0 Qt Version: 6.9.0 Kernel Version: 6.12.30-1-lts (64-bit) Graphics Platform: X11 Processors: 6 × Intel® Core™ i5-9400 CPU @ 2.90GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 ``` ---
**Author:** ![Krovikan](https://discuss-cdn.kde.org/user_avatar/discuss.kde.org/krovikan/32/20043_2.png) [@Krovikan](https://discuss.kde.org/u/Krovikan)\ **Post date:** [May 28, 2025, 6:17pm UTC](https://discuss.kde.org/t/qthreadstorage-warning-in-the-log/29264/10 "2025-05-28T18:17:15Z")
Related thread with Qt 6.9.0: > [@QThreadStorage spamming](https://discuss.kde.org/t/qthreadstorage-spamming/34576): > > Some links show it’s fixed for Qt 6.8.3, but I’m on Plasma 6.3.5 and it continues to spam everything Regards ---
**Author:** ![Arimil](https://discuss-cdn.kde.org/user_avatar/discuss.kde.org/arimil/32/19161_2.png) [@Arimil](https://discuss.kde.org/u/Arimil)\ **Post date:** [April 13, 2026, 5:35pm UTC](https://discuss.kde.org/t/qthreadstorage-warning-in-the-log/29264/11 "2026-04-13T17:35:08Z")
Not meaning to necro this but when looking for this error this is the first thing you will find, in 2026 with Qt 6.11 this issue is being tracked here: > **[510785 – QThreadStorage entry n destroyed before end of thread errors on...](https://bugs.kde.org/show_bug.cgi?id=510785)** And it appears it will be fixed in the next Qt release 6.11.1 scheduled for release April 30th 2026. > **[Qt 6.11 release plan - Qt 6.11 Release - Qt Wiki](https://wiki.qt.io/Qt_6.11_Release#Qt_6.11_release_plan)** > > 16.09.2025 Qt 6.11.0 Initial schedule