Bug 437443

Summary: crash when searching, after start
Product: [Applications] Discover Reporter: Anton K <KVAnton.WEB>
Component: discoverAssignee: Dan Leinir Turthra Jensen <leinir>
Status: RESOLVED DUPLICATE    
Severity: crash CC: aleixpol, nate
Priority: NOR Keywords: drkonqi
Version: 5.21.5   
Target Milestone: ---   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: New crash information added by DrKonqi

Description Anton K 2021-05-21 07:56:47 UTC 
Application: plasma-discover (5.21.5)

Qt Version: 5.15.2
Frameworks Version: 5.82.0
Operating System: Linux 5.11.16-051116-generic x86_64
Windowing System: X11
Drkonqi Version: 5.21.5
Distribution: KDE neon User Edition 5.21

-- Information about the crash:
- What I was doing when the application crashed:

crash when searching for an application after starting Detecting and searching for updates at this time

The crash does not seem to be reproducible.

-- Backtrace (Reduced):
#4  0x00007fdd9dd77ba0 in std::__atomic_base<QThreadData*>::load(std::memory_order) const (__m=std::memory_order_acquire, this=0x200000038) at /usr/include/c++/9/bits/atomic_base.h:734
#5  std::atomic<QThreadData*>::load(std::memory_order) const (__m=std::memory_order_acquire, this=0x200000038) at /usr/include/c++/9/atomic:519
#6  QAtomicOps<QThreadData*>::loadAcquire<QThreadData*>(std::atomic<QThreadData*> const&) (_q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:251
#7  QBasicAtomicPointer<QThreadData>::loadAcquire() const (this=0x200000038) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:255
#8  QBasicAtomicPointer<QThreadData>::operator QThreadData*() const (this=0x200000038) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:251


Possible duplicates by query: bug 422533.

Reported using DrKonqi
Comment 1 Anton K 2021-05-21 07:56:49 UTC 
Created attachment 138633 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 Nate Graham 2021-05-21 15:27:35 UTC 

*** This bug has been marked as a duplicate of bug 433807 ***