[dolphin] [Bug 434456] New: Crash when collapsing detailed view of big folder

2021-03-15 Thread Daniel Halens
https://bugs.kde.org/show_bug.cgi?id=434456

Bug ID: 434456
   Summary: Crash when collapsing detailed view of big folder
   Product: dolphin
   Version: 20.12.2
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: danielhal...@gmail.com
CC: kfm-de...@kde.org
  Target Milestone: ---

Application: dolphin (20.12.2)

Qt Version: 5.15.2
Frameworks Version: 5.79.0
Operating System: Linux 5.8.0-44-generic x86_64
Windowing System: X11
Drkonqi Version: 5.21.1
Distribution: KDE neon User Edition 5.21

-- Information about the crash:
- What I was doing when the application crashed:
Expand a folder with hundreds of subfolders.
Collapse it before Dolphin finishes counting the number of elements inside
those folders.

- Custom settings of the application:
Dolphin set to detailed view.
Previews on at minimum size.

The crash can be reproduced every time.

-- Backtrace:
Application: Dolphin (dolphin), signal: Aborted

[New LWP 3714]
[New LWP 4016]
[New LWP 176771]
[New LWP 265396]
[New LWP 265398]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f2116c78dff in __GI___wait4 (pid=265705, stat_loc=0x0, options=0,
usage=0x0) at ../sysdeps/unix/sysv/linux/wait4.c:27
[Current thread is 1 (Thread 0x7f210fd3a8c0 (LWP 3532))]

Thread 6 (Thread 0x7f20fb7fe700 (LWP 265398)):
#0  futex_abstimed_wait_cancelable (private=,
abstime=0x7f20fb7fdc50, clockid=, expected=0,
futex_word=0x5618f06b7c60) at ../sysdeps/nptl/futex-internal.h:320
#1  __pthread_cond_wait_common (abstime=0x7f20fb7fdc50, clockid=, mutex=0x5618f06b7c10, cond=0x5618f06b7c38) at pthread_cond_wait.c:520
#2  __pthread_cond_timedwait (cond=0x5618f06b7c38, mutex=0x5618f06b7c10,
abstime=0x7f20fb7fdc50) at pthread_cond_wait.c:656
#3  0x7f2114799ca8 in QWaitConditionPrivate::wait_relative
(this=0x5618f06b7c10, deadline=...) at thread/qwaitcondition_unix.cpp:136
#4  QWaitConditionPrivate::wait (deadline=..., this=0x5618f06b7c10) at
thread/qwaitcondition_unix.cpp:144
#5  QWaitCondition::wait (this=this@entry=0x5618f0512100,
mutex=mutex@entry=0x5618f074ff38, deadline=...) at
thread/qwaitcondition_unix.cpp:225
#6  0x7f21147971b1 in QThreadPoolThread::run (this=0x5618f05120f0) at
../../include/QtCore/../../src/corelib/thread/qmutex.h:270
#7  0x7f2114793bac in QThreadPrivate::start (arg=0x5618f05120f0) at
thread/qthread_unix.cpp:329
#8  0x7f211310d609 in start_thread (arg=) at
pthread_create.c:477
#9  0x7f2116cb5293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 5 (Thread 0x7f20f700 (LWP 265396)):
#0  futex_abstimed_wait_cancelable (private=,
abstime=0x7f20ec50, clockid=, expected=0,
futex_word=0x5618f05d4b14) at ../sysdeps/nptl/futex-internal.h:320
#1  __pthread_cond_wait_common (abstime=0x7f20ec50, clockid=, mutex=0x5618f05d4ac0, cond=0x5618f05d4ae8) at pthread_cond_wait.c:520
#2  __pthread_cond_timedwait (cond=0x5618f05d4ae8, mutex=0x5618f05d4ac0,
abstime=0x7f20ec50) at pthread_cond_wait.c:656
#3  0x7f2114799ca8 in QWaitConditionPrivate::wait_relative
(this=0x5618f05d4ac0, deadline=...) at thread/qwaitcondition_unix.cpp:136
#4  QWaitConditionPrivate::wait (deadline=..., this=0x5618f05d4ac0) at
thread/qwaitcondition_unix.cpp:144
#5  QWaitCondition::wait (this=this@entry=0x5618f0631970,
mutex=mutex@entry=0x5618f074ff38, deadline=...) at
thread/qwaitcondition_unix.cpp:225
#6  0x7f21147971b1 in QThreadPoolThread::run (this=0x5618f0631960) at
../../include/QtCore/../../src/corelib/thread/qmutex.h:270
#7  0x7f2114793bac in QThreadPrivate::start (arg=0x5618f0631960) at
thread/qthread_unix.cpp:329
#8  0x7f211310d609 in start_thread (arg=) at
pthread_create.c:477
#9  0x7f2116cb5293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 4 (Thread 0x7f20faffd700 (LWP 176771)):
#0  __GI___libc_read (nbytes=10, buf=0x7f20faffcb1e, fd=32) at
../sysdeps/unix/sysv/linux/read.c:26
#1  __GI___libc_read (fd=32, buf=0x7f20faffcb1e, nbytes=10) at
../sysdeps/unix/sysv/linux/read.c:24
#2  0x7f21122c0975 in pa_read () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so
#3  0x7f21130ba416 in pa_mainloop_prepare () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#4  0x7f21130baeb4 in pa_mainloop_iterate () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#5  0x7f21130baf70 in pa_mainloop_run () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#6  0x7f21130c911d in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
#7  0x7f21122ef72c in ?? () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so
#8  0x7f211310d609 in start_thread (arg=) at
pthread_create.c:477
#9  0x7f2116cb5293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

[kwin] [Bug 402976] New: KWin crash after resuming from suspend

2019-01-07 Thread Daniel Halens
https://bugs.kde.org/show_bug.cgi?id=402976

Bug ID: 402976
   Summary: KWin crash after resuming from suspend
   Product: kwin
   Version: 5.14.4
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: danielhal...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.14.4)

Qt Version: 5.11.2
Frameworks Version: 5.53.0
Operating System: Linux 4.18.0-13-generic x86_64
Distribution: KDE neon User Edition 5.14

-- Information about the crash:
- What I was doing when the application crashed:
Just resumed from suspend.
Issue happens only sometimes and I don't recall having anything different from
other times.

- Custom settings of the application:
Nvidia propietary drivers 415.25
IIRC, I have the default settings for desktop effects

The crash can be reproduced sometimes.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f8764905840 (LWP 9681))]

Thread 8 (Thread 0x7f872700 (LWP 17654)):
#0  0x7f8764270cf6 in __GI_ppoll (fds=fds@entry=0x7f87280014c8,
nfds=nfds@entry=1, timeout=, timeout@entry=0x0,
sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39
#1  0x7f8761870d51 in ppoll (__ss=, __timeout=, __nfds=, __fds=) at
/usr/include/x86_64-linux-gnu/bits/poll2.h:77
#2  0x7f8761870d51 in qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7f87280014c8)
at kernel/qcore_unix.cpp:132
#3  0x7f8761870d51 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
(fds=0x7f87280014c8, nfds=1, timeout_ts=timeout_ts@entry=0x0) at
kernel/qcore_unix.cpp:153
#4  0x7f876187245e in
QEventDispatcherUNIX::processEvents(QFlags)
(this=, flags=...) at kernel/qeventdispatcher_unix.cpp:500
#5  0x7f876181930a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f872fffed40, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:214
#6  0x7f8761644bba in QThread::exec() (this=this@entry=0x7f8744036100) at
thread/qthread.cpp:525
#7  0x7f875bd344f5 in QQmlThreadPrivate::run() (this=0x7f8744036100) at
qml/ftw/qqmlthread.cpp:148
#8  0x7f876164fadb in QThreadPrivate::start(void*) (arg=0x7f8744036100) at
thread/qthread_unix.cpp:367
#9  0x7f875d2a86db in start_thread (arg=0x7f872700) at
pthread_create.c:463
#10 0x7f876427d88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 7 (Thread 0x7f8742dad700 (LWP 30178)):
#0  0x7f8764270cf6 in __GI_ppoll (fds=fds@entry=0x563556156378,
nfds=nfds@entry=1, timeout=, timeout@entry=0x0,
sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39
#1  0x7f8761870d51 in ppoll (__ss=, __timeout=, __nfds=, __fds=) at
/usr/include/x86_64-linux-gnu/bits/poll2.h:77
#2  0x7f8761870d51 in qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x563556156378)
at kernel/qcore_unix.cpp:132
#3  0x7f8761870d51 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
(fds=0x563556156378, nfds=1, timeout_ts=timeout_ts@entry=0x0) at
kernel/qcore_unix.cpp:153
#4  0x7f876187245e in
QEventDispatcherUNIX::processEvents(QFlags)
(this=, flags=...) at kernel/qeventdispatcher_unix.cpp:500
#5  0x7f876181930a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f8742dacd60, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:214
#6  0x7f8761644bba in QThread::exec() (this=) at
thread/qthread.cpp:525
#7  0x7f876164fadb in QThreadPrivate::start(void*) (arg=0x563555e94590) at
thread/qthread_unix.cpp:367
#8  0x7f875d2a86db in start_thread (arg=0x7f8742dad700) at
pthread_create.c:463
#9  0x7f876427d88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 6 (Thread 0x7f872d371700 (LWP 16725)):
#0  0x7f875d2ae9f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x563555e97d10) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f875d2ae9f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x563555e97cc0, cond=0x563555e97ce8) at pthread_cond_wait.c:502
#2  0x7f875d2ae9f3 in __pthread_cond_wait (cond=0x563555e97ce8,
mutex=0x563555e97cc0) at pthread_cond_wait.c:655
#3  0x7f876165094b in QWaitConditionPrivate::wait(unsigned long)
(time=18446744073709551615, this=0x563555e97cc0) at
thread/qwaitcondition_unix.cpp:143
#4  0x7f876165094b in QWaitCondition::wait(QMutex*, unsigned long)
(this=this@entry=0x7f87440232d8, mutex=mutex@entry=0x7f87440232d0,
time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215
#5  0x7f875c45ab18 in QSGRenderThreadEventQueue::takeEvent(bool)
(wait=true, this=0x7f87440232c8) at scenegraph/qsgthreadedrenderloop.cpp:245
#6  0x7f875c45ab18 in QSGRenderThread::processEventsAndWaitForMore()
(this=this@entry=0x7f8744023250) at scenegraph/qsgthreadedrenderloop.cpp:709
#7  0x7f875c45af4a in 

[kwin] [Bug 399358] New: KWin crash after suspend

2018-10-03 Thread Daniel Halens
https://bugs.kde.org/show_bug.cgi?id=399358

Bug ID: 399358
   Summary: KWin crash after suspend
   Product: kwin
   Version: 5.13.5
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: danielhal...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.13.5)

Qt Version: 5.11.1
Frameworks Version: 5.50.0
Operating System: Linux 4.13.0-45-generic x86_64
Distribution: KDE neon User Edition 5.13

-- Information about the crash:
- What I was doing when the application crashed:
When I turned on the computer after suspending it, there was the drkonqui
notification saying the trace is useful (hopefully it actually is). I didn't
loose the desktop effects or anything so I guess it restarted without me
noticing at all.
- Graphic cards info:
Asus ROG laptop with
· Nvidia GTX 960M with propietary drivers 396.54 (always using this one)
· Intel HD 530

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f71e689e840 (LWP 23845))]

Thread 7 (Thread 0x7f71c5eaa700 (LWP 28486)):
#0  0x7f71e61fccf6 in __GI_ppoll (fds=0x55a2b2ee8568, nfds=1,
timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39
#1  0x7f71e35e27a1 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f71e35e3eae in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f71e358adea in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f71e33b5b8a in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f71e33c0aab in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f71df2456db in start_thread (arg=0x7f71c5eaa700) at
pthread_create.c:463
#7  0x7f71e620988f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 6 (Thread 0x7f71b3c06700 (LWP 26191)):
#0  0x7f71df24b9f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x55a2b33b9510) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f71df24b9f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x55a2b33b94c0, cond=0x55a2b33b94e8) at pthread_cond_wait.c:502
#2  0x7f71df24b9f3 in __pthread_cond_wait (cond=0x55a2b33b94e8,
mutex=0x55a2b33b94c0) at pthread_cond_wait.c:655
#3  0x7f71e33c191b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f71de3f7be8 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7f71de3f801a in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#6  0x7f71e33c0aab in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f71df2456db in start_thread (arg=0x7f71b3c06700) at
pthread_create.c:463
#8  0x7f71e620988f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 5 (Thread 0x7f71b2c1b700 (LWP 23903)):
#0  0x7f71df24b9f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x7f71e27ebfb8) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f71df24b9f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x7f71e27ebf68, cond=0x7f71e27ebf90) at pthread_cond_wait.c:502
#2  0x7f71df24b9f3 in __pthread_cond_wait (cond=0x7f71e27ebf90,
mutex=0x7f71e27ebf68) at pthread_cond_wait.c:655
#3  0x7f71e24f6954 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#4  0x7f71e24f6999 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#5  0x7f71df2456db in start_thread (arg=0x7f71b2c1b700) at
pthread_create.c:463
#6  0x7f71e620988f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 4 (Thread 0x7f71b700 (LWP 23900)):
#0  0x7f71e61fccf6 in __GI_ppoll (fds=0x7f71b4000d28, nfds=1,
timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39
#1  0x7f71e35e27a1 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f71e35e3eae in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f71e358adea in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f71e33b5b8a in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f71ddcd28b5 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#6  0x7f71e33c0aab in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f71df2456db in start_thread (arg=0x7f71b700) at
pthread_create.c:463
#8  0x7f71e620988f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7f71c7341700 (LWP 23896)):
#0  0x7f71e61fccf6 in __GI_ppoll (fds=0x7f71c000ef08, nfds=1,
timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39
#1  

[Discover] [Bug 387630] Discover Plasma Addons Possible Memory Leak

2018-01-16 Thread Daniel Halens Rodriguez
https://bugs.kde.org/show_bug.cgi?id=387630

Daniel Halens Rodriguez <danielhal...@gmail.com> changed:

   What|Removed |Added

 CC||danielhal...@gmail.com

--- Comment #4 from Daniel Halens Rodriguez <danielhal...@gmail.com> ---
(In reply to Ivan S from comment #2)
> (In reply to Ivan S from comment #1)
> > (In reply to r.doherty from comment #0)
> > > Discover Menu's all working as normal besides "Plasma Addons". Once 
> > > entered
> > > the side menu will attempt to load a list of the addons, as this happens
> > > (and fails) the program will gradually consume more and more RAM until the
> > > entirety of the systems RAM is consumed causing a litany of errors that
> > > required a hard shut down.
> > Run in the command prompt: 
> > plasma-discover >> discover_out.txt
> > and post the output. I can't seem to replicate this same bug.
> Actually I can confirm this. The leak is very slow, however, and no useful
> output is generated from plasma-discover >> discover-out.txt. When clicking
> Plasma Addons, the following appears in the log:
> stream took really long "KNS-search-plasma-themes.knsrc"
> stream took really long "KNS-search-wallpaper.knsrc"
> stream took really long "KNS-search-cgcgtk3.knsrc"
> stream took really long "KNS-search-xcursor.knsrc"
> stream took really long "KNS-search-cgctheme.knsrc"
> stream took really long "KNS-search-icons.knsrc"
> stream took really long "AggregatedResultsStream"
> Not sure if this is a memory leak though. It may just be Plasma trying to
> load the entirety of the OpenDesktop database into RAM - databases like that
> can be as big as 1tb. Discover does not seem to work under valgrind, which
> makes leak detection hard.
I can confirm the bug on 5.11.5
On my system, the leak is very fast (about 1GB / 10 secs!)
I found out that clicking quickly on any section under Plasma Addons will avoid
the bug until going back and entering again.

-- 
You are receiving this mail because:
You are watching all bug changes.