Summary: | Dolphin crashes when right-clicking on file or folder to summon the contextual menu | ||
---|---|---|---|
Product: | [Applications] dolphin | Reporter: | Paul Brown <paul.brown> |
Component: | general | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | jodr666, jordan.bucklin, josealbertogonzalez, kfm-devel |
Priority: | NOR | Keywords: | drkonqi |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | https://invent.kde.org/network/kio-extras/commit/07d54af0b6e3f074a9e679db506fc538f52cc410 | Version Fixed In: | |
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Paul Brown
2021-07-15 09:33:10 UTC
This is happening for me as well, specifically once I mouse-over the Activities option. Does your context menu stay open at all without moving the mouse? Git commit 07d54af0b6e3f074a9e679db506fc538f52cc410 by Harald Sitter. Committed on 15/07/2021 at 14:01. Pushed by sitter into branch 'release/21.08'. don't auto deduce QStringBuilder see 'auto QString(Builder) considered VERY HARMFUL' thread on kde-devel https://markmail.org/message/mbrp5ypyhcfk7zjn What happens is that the type of str ends up being QStringBuilder instead of QString. The QStringBuilder is destroyed after the semicolon, and all access to "str" produces undefined behavior. Never use auto for QString concatenation! M +1 -1 activities/fileitemplugin/FileItemLinkingPluginActionLoader.cpp https://invent.kde.org/network/kio-extras/commit/07d54af0b6e3f074a9e679db506fc538f52cc410 Created attachment 140092 [details]
New crash information added by DrKonqi
dolphin (21.07.80) using Qt 5.15.3
- What I was doing when the application crashed: dolphin crashed when I do a right click over an image or folder, ever and ever
-- Backtrace (Reduced):
#4 std::__atomic_base<int>::load (__m=std::memory_order_relaxed, this=<optimized out>) at /usr/include/c++/9/bits/atomic_base.h:413
#5 QAtomicOps<int>::loadRelaxed<int> (_q_value=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qatomic_cxx11.h:239
#6 QBasicAtomicInteger<int>::loadRelaxed (this=<optimized out>) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qbasicatomic.h:107
[...]
#8 QString::QString (other=..., this=0x7fe3efce6bc0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:1094
#9 QStringBuilder<QString, QString>::operator QString (this=<synthetic pointer>, this=<synthetic pointer>) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qstringbuilder.h:147
(In reply to Harald Sitter from comment #2) > Git commit 07d54af0b6e3f074a9e679db506fc538f52cc410 by Harald Sitter. > Committed on 15/07/2021 at 14:01. > Pushed by sitter into branch 'release/21.08'. > > don't auto deduce QStringBuilder > > see 'auto QString(Builder) considered VERY HARMFUL' thread on kde-devel > https://markmail.org/message/mbrp5ypyhcfk7zjn > > What happens is that the type of str ends up being QStringBuilder > instead of QString. The QStringBuilder is destroyed after the semicolon, > and all access to "str" produces undefined behavior. > > Never use auto for QString concatenation! > > M +1 -1 > activities/fileitemplugin/FileItemLinkingPluginActionLoader.cpp > > https://invent.kde.org/network/kio-extras/commit/ > 07d54af0b6e3f074a9e679db506fc538f52cc410 Thanks, Harald! *** Bug 439651 has been marked as a duplicate of this bug. *** |