Bug 383942

Summary:	Application: Dolphin (kdeinit5), signal: Aborted
Product:	[Applications] dolphin	Reporter:	Robert Laney <bobylaney>
Component:	general	Assignee:	Dolphin Bug Assignee <dolphin-bugs-null>
Status:	RESOLVED FIXED
Severity:	crash	CC:	elvis.angelaccio, justin.zobel, mail
Priority:	NOR
Version First Reported In:	16.12.3
Target Milestone:	---
Platform:	Mageia RPMs
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	Valgrind output of the bug

Description Robert Laney 2017-08-24 10:12:28 UTC

By closing Dolphin either by the "x" window button or by menu file exit
kdeinit reports error "signal aborted"

trace shows signal raised from memory free operation into nvidia drivers libs ?

No special activity in dolphin : just displaying directories and files
French locale
left Panels : "Emplacements" + "Dossiers"
right pannel : "Information"

Frequency : ~7/10 times (not always)

 2017-08-24
 
Application: kdeinit5 (kdeinit5), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb971773800 (LWP 21913))]

Thread 2 (Thread 0x7fb953fff700 (LWP 21915)):
[KCrash Handler]
#6  0x00007fb96fc77818 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55
#7  0x00007fb96fc78f2a in __GI_abort () at abort.c:89
#8  0x00007fb96fcb643a in __libc_message (do_abort=2, fmt=fmt@entry=0x7fb96fdc0900 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
#9  0x00007fb96fcbd246 in malloc_printerr (ar_ptr=0x7fb94c000020, ptr=0x7fb94c0008b0, str=0x7fb96fdbe218 "corrupted double-linked list", action=<optimized out>) at malloc.c:5007
#10 0x00007fb96fcbd246 in malloc_consolidate (av=av@entry=0x7fb94c000020) at malloc.c:4176
#11 0x00007fb96fcc0b27 in _int_malloc (av=av@entry=0x7fb94c000020, bytes=bytes@entry=2032) at malloc.c:3451
#12 0x00007fb96fcc35b3 in __libc_calloc (n=<optimized out>, elem_size=<optimized out>) at malloc.c:3237
#13 0x00007fb96b99b3e3 in  () at /usr/lib64/nvidia-current/tls/libnvidia-tls.so.384.59
#14 0x00007fb96c92bed1 in g_malloc0 (n_bytes=2032) at gmem.c:124
#15 0x00007fb96c94493d in thread_memory_from_self () at gslice.c:519
#16 0x00007fb96c94493d in g_slice_free1 (mem_size=<optimized out>, mem_block=0x838b00) at gslice.c:1112
#17 0x00007fb96d6743d9 in __nptl_deallocate_tsd () at pthread_create.c:176
#18 0x00007fb96d675809 in __nptl_deallocate_tsd () at pthread_create.c:327
#19 0x00007fb96d675809 in start_thread (arg=0x7fb953fff700) at pthread_create.c:347
#20 0x00007fb96fd39e4d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fb971773800 (LWP 21913)):
#0  0x00007fb96b999e15 in _nv014tls () at /usr/lib64/nvidia-current/tls/libnvidia-tls.so.384.59
#1  0x00007fb96e0b6c7d in  () at /usr/lib64/nvidia-current/libGL.so.1
#2  0x00007fb96e0b705b in  () at /usr/lib64/nvidia-current/libGL.so.1
#3  0x00007fb96e0b714a in  () at /usr/lib64/nvidia-current/libGL.so.1
#4  0x00007fb96e0fc4da in  () at /usr/lib64/nvidia-current/libGL.so.1
#5  0x00007fb971634a35 in _dl_fini () at dl-fini.c:257
#6  0x00007fb96fc7a468 in __run_exit_handlers (status=0, listp=0x7fb96fff1618 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82
#7  0x00007fb96fc7a4b5 in __GI_exit (status=<optimized out>) at exit.c:104
#8  0x0000000000408196 in launch(int, char const*, char const*, char const*, int, char const*, bool, char const*, bool, char const*) ()
#9  0x0000000000409437 in handle_launcher_request(int, char const*) [clone .isra.26] ()
#10 0x0000000000409bd6 in handle_requests(int) ()
#11 0x0000000000404dd3 in main ()

Comment 1 Elvis Angelaccio 2017-08-24 14:16:36 UTC

Yes, that's the nvidia driver. I'd suggest you to report this to your distribution or even upstream Nvidia.

Comment 2 Christoph Feck 2017-08-24 21:19:06 UTC

A valgrind log would help to understand if the the memory corruption is caused by the nvidia driver or KDE code.

For more information, please see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_with_Valgrind

Comment 3 Robert Laney 2017-11-29 10:15:04 UTC

Created attachment 109110 [details]
Valgrind output of the bug

I'm new to Valgrind so I don't really know if this file can help to track this issue

Comment 4 Julian Steinmann 2018-06-29 19:34:30 UTC

First: Thanks for uploading the valgrind log! The version you were using to originally report this bug is now severely outdated. Could you try to update Dolphin and reproduce this crash again? If the bug does still occur, a new valgrind log would be helpful as this would represent the current state of the cod e better. Thanks!

Comment 5 Robert Laney 2018-07-04 14:43:40 UTC

Hi Julian,

I "solved" the bug by re-installing completely mageia 6 distro including 
KDE.

The problem disappeared so far. So, I can't redo a Valgrind log from 
this Dolphin crash.

(I will do it if it occurs again :-( )

Sorry,

BL



Le 29/06/2018 à 21:34, Julian Schraner a écrit :
> https://bugs.kde.org/show_bug.cgi?id=383942
>
> Julian Schraner <juliquadrat@gmail.com> changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>           Resolution|---                         |WAITINGFORINFO
>                   CC|                            |juliquadrat@gmail.com
>               Status|UNCONFIRMED                 |NEEDSINFO
>
> --- Comment #4 from Julian Schraner <juliquadrat@gmail.com> ---
> First: Thanks for uploading the valgrind log! The version you were using to
> originally report this bug is now severely outdated. Could you try to update
> Dolphin and reproduce this crash again? If the bug does still occur, a new
> valgrind log would be helpful as this would represent the current state of the
> cod e better. Thanks!
>

Comment 6 Julian Steinmann 2018-07-18 19:17:56 UTC

Thanks for the update, changing the status until somebody experiences this bug again.

Comment 7 Justin Zobel 2020-12-01 04:15:31 UTC

Marking as resolved as no other user has commented on this or marked a duplicate.