Bug 461352

Summary: Interaction with the file dialog sometimes crashes plasmashell
Product: [Plasma] plasmashell Reporter: Martin van Es <bugs>
Component: generic-crashAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED REMIND    
Severity: crash CC: nate
Priority: NOR    
Version First Reported In: 5.26.2   
Target Milestone: 1.0   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: plasmashell crash log

Description Martin van Es 2022-11-03 11:00:47 UTC
Created attachment 153434 [details]
plasmashell crash log

SUMMARY
On certain occasions (I can not reliably reproduce all interactions, but it happens often) plasmashell crashes after interacting with the file dialog. I run plasmashell in a wayland context.

STEPS TO REPRODUCE
1. Open native KDE file dialog (either to select files to load, or to select save to location) from any application
2. Close dialog by either pressing OK or Cancel (both crash plasmashell)

OBSERVED RESULT
Plasmashell crashes
The plasmashell crash starts with "free(): invalid next size (fast)"
No Dr. Konqi to inspect debug symbols

EXPECTED RESULT
No plasmashell crash

SOFTWARE/OS VERSIONS
Operating System: Kubuntu 22.10
KDE Plasma Version: 5.26.2
KDE Frameworks Version: 5.99.0
Qt Version: 5.15.6
Kernel Version: 6.0.6 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz
Memory: 31.1 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics
Manufacturer: Notebook
Product Name: N141CU
System Version: Not Applicable
Comment 1 Martin van Es 2022-11-03 12:47:09 UTC
I can even reproduce with these at the moment:
$ kdialog --getsavefilename .
$ kdialog --getopenfilename .
Comment 2 Nate Graham 2022-11-04 17:07:12 UTC
That's odd. Note that when something crashes, we need a backtrace of it so we can figure out what's going on. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports.

Can you please attach one? Thanks!
Comment 3 Martin van Es 2022-11-05 14:08:25 UTC
Like I said in the report, Dr. Konqi fails to catch the crash so I'm lost at the only hint that says: free(): invalid next size (fast)
I'm sorry, and it seems like some sort of deterioration of the desktop because I never encounter the problem after a cold boot. So, even when very much present, it's hard to reproduce at all times (at least, I don't know what's triggering it, yet).
Comment 4 Bug Janitor Service 2022-11-20 05:11:55 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Martin van Es 2022-11-22 17:28:49 UTC
Since I can not easily reproduce and get Dr. Konqi to pick up the pieces, let's just close the ticket and let me lick my wounds.