Application: plasma-discover (6.1.4) Qt Version: 6.7.2 Frameworks Version: 6.5.0 Operating System: Linux 6.10.3-200.fc40.x86_64 x86_64 Windowing System: Wayland Distribution: "Fedora Linux 40 (KDE Plasma)" DrKonqi: 6.1.4 [CoredumpBackend] -- Information about the crash: After launching the Discover program it automatically starts fetching for updates like noramal. When its done fetching updates I can see the available updates listed. Before I can do anything Discover just suddenly quits. I can keep reproducing the issue. The crash can be reproduced every time. -- Backtrace (Reduced): #5 std::__atomic_base<int>::fetch_add (this=0x100, __i=1, __m=std::memory_order_acq_rel) at /usr/include/c++/14/bits/atomic_base.h:629 #6 QAtomicOps<int>::ref<int> (_q_value=<error reading variable: Cannot access memory at address 0x100>) at /usr/src/debug/qt6-qtbase-6.7.2-4.fc40.x86_64/src/corelib/thread/qatomic_cxx11.h:259 [...] #8 QtSharedPointer::ExternalRefCountData::getAndRef (obj=obj@entry=0x55fbd4ffd3d0) at /usr/src/debug/qt6-qtbase-6.7.2-4.fc40.x86_64/src/corelib/tools/qsharedpointer.cpp:1456 #9 0x00007f3b8463ed2a in QV4::QV4QPointer<QObject>::init (this=0x7f3ac8a6ef98, o=0x55fbd4ffd3d0) at /usr/src/debug/qt6-qtdeclarative-6.7.2-2.fc40.x86_64/src/qml/memory/qv4heap_p.h:175 #10 QV4::QV4QPointer<QObject>::init (this=0x7f3ac8a6ef98, o=0x55fbd4ffd3d0) at /usr/src/debug/qt6-qtdeclarative-6.7.2-2.fc40.x86_64/src/qml/memory/qv4heap_p.h:175 Reported using DrKonqi
Created attachment 172598 [details] New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace.
> #6 QAtomicOps<int>::ref<int> (_q_value=<error reading variable: Cannot access memory at address 0x100>) at /usr/src/debug/qt6-qtbase-6.7.2-4.fc40.x86_64/src/corelib/thread/qatomic_cxx11.h:259 Memory corruption?
Created attachment 172628 [details] attachment-463626-0.html Hello So are you thinking bad RAM? I also run Debian 12 KDE on this same machine. KDE 5.27 and cannot reproduce the issue. At least not yet. Does that make sense? On Wed, Aug 14, 2024 at 2:36 PM Nate Graham <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=491689 > > Nate Graham <nate@kde.org> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |nate@kde.org > > --- Comment #2 from Nate Graham <nate@kde.org> --- > > #6 QAtomicOps<int>::ref<int> (_q_value=<error reading variable: Cannot > access memory at address 0x100>) at > /usr/src/debug/qt6-qtbase-6.7.2-4.fc40.x86_64/src/corelib/thread/qatomic_cxx11.h:259 > > Memory corruption? > > -- > You are receiving this mail because: > You reported the bug.
In Bug 491760, you said you made some memory adjustments, and in that bug report it's crashing with a different backtrace, so I guess there was indeed some type of hardware issue.
Created attachment 172767 [details] attachment-1665497-0.html Hello again. Well I replaced the RAM but Discover still crashes. Everything else runs fine. Strange. Not sure what to do next. It’s just Discover. No other errors appear. Any other suggestions? Thanks for your help Derek Enz On Fri, Aug 16, 2024 at 8:17 AM Nate Graham <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=491689 > > Nate Graham <nate@kde.org> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Status|REPORTED |RESOLVED > Resolution|--- |DOWNSTREAM > > --- Comment #4 from Nate Graham <nate@kde.org> --- > In Bug 491760, you said you made some memory adjustments, and in that bug > report it's crashing with a different backtrace, so I guess there was > indeed > some type of hardware issue. > > -- > You are receiving this mail because: > You reported the bug.
Ok after doing more research I ran in Fedora a dnf refresh update. This downloaded a few new Mesa driver updates. Since then Discover seems to be working fine. Does that make sense?
Yep, that could indeed have fixed it.
(In reply to Nate Graham from comment #7) > Yep, that could indeed have fixed it. Awesome! Thank you!