| Summary: | CTD malloc(): unaligned tcache chunk detected | ||
|---|---|---|---|
| Product: | [Applications] knetwalk | Reporter: | Lone_Wolf <Lone_Wolf> |
| Component: | general | Assignee: | Ashwin Rajeev <ashwin_rajeev> |
| Status: | REPORTED --- | ||
| Severity: | normal | CC: | aacid, kde-games-bugs-null, Lone_Wolf |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
valgrind log from starting & closing knetwalk
journal snippet of drkonqi during knetwalk crash crash log with coredump info CTD log with debug info 2024-06-07 approx 01:10 crash log with lots more debug symbols |
||
|
Description
Lone_Wolf
2024-04-23 12:57:03 UTC
> When clicking new in menu knetwalk occasionally crashes to desktop. There's sadly nothing really problematic in that valgrind trace. If you could submit the crash report that happens when you get the crash (drkonqui) it could give us some pointer. For other devels, i've found https://crash-reports.kde.org/organizations/kde/issues/11014/ that may be this, but the backtrace is rather not super useful. (In reply to Albert Astals Cid from comment #1) > > When clicking new in menu knetwalk occasionally crashes to desktop. > > There's sadly nothing really problematic in that valgrind trace. > > If you could submit the crash report that happens when you get the crash > (drkonqui) it could give us some pointer. > > For other devels, i've found > https://crash-reports.kde.org/organizations/kde/issues/11014/ that may be > this, but the backtrace is rather not super useful. I installed drkonqi and debug symbols for knetwalk . gdb and debuginfod are also installed. Drkonqi is triggered when knetwalk crashes, but claims the crash report (attached) is not useful. I'll need more guidance. Created attachment 168842 [details]
journal snippet of drkonqi during knetwalk crash
Created attachment 168930 [details]
crash log with coredump info
I had coredumps disabled (building a certain compiler gives lots of coredumps that only hinder the build and have no other purpose as far as I know ) and it seems dr konqi needs them.
new dr konqi crash report attached, hope this helps.
It's crashing in "new" which is like if you were running out of memory or something, are you running some weird kernel or libc or something that tries to be "extra secure" by limiting the memory usage? (In reply to Albert Astals Cid from comment #5) > It's crashing in "new" which is like if you were running out of memory or > something, are you running some weird kernel or libc or something that tries > to be "extra secure" by limiting the memory usage? 16 GiB ram, swapfile of 24 GiB . Packages from archlinux official repos, kernel config & build files at https://gitlab.archlinux.org/archlinux/packaging/packages/linux/-/blob/9f042c5b72f15799ec45d5acec115dfa2b2caf34/config I'm 99% sure the crashes started after archlinux switched to Qt 6.7.0 early in april, but haven't occured in the past 2 weeks. Could Qt be involved ? Just had another crash, but crash reporter was disabled so no logs. (re-enabled now) Versions KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Knetwalk version 24.05.0 kernel 6.9.3 I'm also on archlinux and can't reproduce this crash at all. Do i understand that just opening knetwalk, and pressing and holding Ctrl+N will make it crash eventually for you? after how much time? Which difficulty and theme are you using? Which Qt style are you using? if you do knetwalk -style blo what styles tell you that you have available? (In reply to Albert Astals Cid from comment #8) > I'm also on archlinux and can't reproduce this crash at all. > > Do i understand that just opening knetwalk, and pressing and holding Ctrl+N > will make it crash eventually for you? after how much time? Nope, start knetwalk play until solved click new often no problem, sometimes the described crash . I just encountered a crash again , attached the log. > > Which difficulty and theme are you using? from ~/config/knetwalkrc [KgDifficulty] Level=Hard [KgTheme] Theme=themes/electronic.desktop > > Which Qt style are you using? if you do knetwalk -style blo what styles > tell you that you have available? $ knetwalk --style blo QApplication: invalid style override 'blo' passed, ignoring it. Available styles: Oxygen, Windows, Fusion [ALSOFT] (EE) Could not query RTKit: No such file or directory (2) $ Created attachment 170215 [details]
CTD log with debug info 2024-06-07 approx 01:10
No idea how to verify the used style. I don't use/have installed systemsettings. Running lxqt as DE with openbox as WM so I expect the style to be Fusion . Created attachment 170470 [details]
crash log with lots more debug symbols
Checking previious logs showed radeonsi_dri.so and libc.so.6 as missing debug symbols .
I installed debug symbol pacakges for my mesa trunk build and glibc, and attached a fresh crash log with a lot more info .
|