Bug 487550

Summary:	KDevelop crashed just after startup
Product:	[Applications] kdevelop	Reporter:	Steven Robbins <steve>
Component:	general	Assignee:	kdevelop-bugs-null
Status:	REPORTED ---
Severity:	crash	Keywords:	drkonqi
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Debian unstable
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	New crash information added by DrKonqi

Description Steven Robbins 2024-05-25 20:34:00 UTC

Application: kdevelop (5.12.230801 (23.08.1))

Qt Version: 5.15.13
Frameworks Version: 5.115.0
Operating System: Linux 6.8.9-amd64 x86_64
Windowing System: X11
Distribution: Debian GNU/Linux trixie/sid
DrKonqi: 5.27.11 [CoredumpBackend]

-- Information about the crash:
I started kdevelop (for the first time in months).  It opened as normal, and I was looking through the sessions list, thinking I might want to create a new session.  I may have clicked on one of the existing sessions, but I'm not certain.  Then the window abruptly vanished.

The reporter is unsure if this crash is reproducible.

-- Backtrace (Reduced):
#3  __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
#4  0x00007fbc39ca6b7f in __pthread_kill_internal (signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:78
#5  0x00007fbc39c584e2 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#6  0x00007fbc39c414ed in __GI_abort () at ./stdlib/abort.c:79
[...]
#8  0x00007fbc39cb0465 in malloc_printerr (str=str@entry=0x7fbc39db9c60 "tcache_thread_shutdown(): unaligned tcache chunk detected") at ./malloc/malloc.c:5765


Reported using DrKonqi

Comment 1 Steven Robbins 2024-05-25 20:34:02 UTC

Created attachment 169834 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.

Comment 2 Steven Robbins 2024-05-25 21:00:28 UTC

When I ran kdev again, I saw a message saying that "crash may have been a result of corrupt cache", with option to clear the cache.  I chose to clear the cache and was able to use kdev without further crashes.